stripe_create_payment_intent
AI agents use stripe_create_payment_intent to commit financial operations through Integrations MCP — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool creates payment intents on Stripe, which is a financial operation that commits or initiates money movement. Even though the description is empty, the tool name combined with the server context (Stripe is explicitly mentioned as a major SaaS platform integrated) and the nature of Stripe's API makes the financial classification unambiguous.
From the tool's definition Tool name 'stripe_create_payment_intent' combined with Stripe context (a major payment processing platform) indicates creation of payment intents, which are financial transactions.
Attacks that exploit this kind of access
stripe_create_payment_intent. It is categorised as a Financial tool in the Integrations MCP MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Integrations MCP server in PolicyLayer and add a rule for stripe_create_payment_intent: 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 Integrations MCP. Nothing to install.
stripe_create_payment_intent is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the stripe_create_payment_intent 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 stripe_create_payment_intent. 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.
stripe_create_payment_intent is provided by the Integrations MCP server (shriram-vasudevan/integrations-mcp). 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 →