Skip to content

Add billing MCP server (refund + delete tools) - #1

Open
rajaramr7 wants to merge 1 commit into
mainfrom
demo/add-billing-mcp
Open

rajaramr7 wants to merge 1 commit into
mainfrom
demo/add-billing-mcp

Conversation

@rajaramr7

Copy link
Copy Markdown
Owner

Adds a new in-house MCP server (billing_mcp_server.py) exposing an issue_refund (financial) and delete_account (destructive) tool to the model, with no human-approval step.

This is net-new high-risk AI surface. The ai-surface CI gate (fail-on: high) should flag it and fail the check, while leaving the repo's 22 pre-existing MCP servers alone (they are not new). Demonstrates: only the AI risk a PR introduces can block it.

@github-actions

github-actions Bot commented Jun 30, 2026

Copy link
Copy Markdown

After this PR merges: 23 total AI surfaces, 47 total risk indicators · 1 high, 22 medium.

🤖 AI Surface Changes

1 new

➕ New AI surfaces

  • MCP Server (in-house): billing_mcp_server.py
    • Tools/permissions: get_invoice, issue_refund, delete_account
    • Files: billing_mcp_server.py
    • ⚠️ in-house MCP server (custom code, audit recommended)
    • ⚠️ unverified source
    • ⚠️ financial action exposed
    • Validate this surface →

Powered by ai-surface. Useful? Star the repo so more engineers find it. Validate which of these surfaces are exploitable: apisec.ai/products.

@rajaramr7
rajaramr7 force-pushed the demo/add-billing-mcp branch from 5e901d1 to 3dc99ec Compare July 9, 2026 20:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant