Remove the Stripe Connect link from a project
AI agents use disconnect_stripe to create or update resources in Prowpt MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Prowpt MCP Server environment.
Disconnecting Stripe is a reversible modification of project settings/configuration. While it affects financial infrastructure (Stripe integration), the action itself does not move money, process refunds, or create financial obligations — it merely severs the connection to a payment processor. This makes it Write rather than Financial.
From the tool's definition Tool description states 'Remove the Stripe Connect link from a project' — this modifies project configuration by disconnecting payment processing integration.
Attacks that exploit this kind of access
Remove the Stripe Connect link from a project. It is categorised as a Write tool in the Prowpt MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Prowpt MCP Server MCP server in PolicyLayer and add a rule for disconnect_stripe: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches Prowpt MCP Server. Nothing to install.
disconnect_stripe is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the disconnect_stripe rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.
Set action: deny in the PolicyLayer policy for disconnect_stripe. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.
disconnect_stripe is provided by the Prowpt MCP Server MCP server (prowptai/prowpt-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →