AI agents use stripe_create_payment to commit financial operations through VibeServe — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool directly creates payment intents, which commits financial obligations and initiates money movement. An AI agent misusing this tool could fraudulently create charges, process unauthorized payments, or bind the user to unintended financial commitments. This is the highest-severity category per the classification rules.
From the tool's definition Tool name 'stripe_create_payment' and description 'Create a Stripe payment intent' explicitly indicate creation of financial payment objects through Stripe, a payment processor.
Attacks that exploit this kind of access
Create a Stripe payment intent. It is categorised as a Financial tool in the VibeServe MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the VibeServe MCP server in PolicyLayer and add a rule for stripe_create_payment: 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 VibeServe. Nothing to install.
stripe_create_payment 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 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. 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 is provided by the VibeServe MCP server (ncsound919/vibeserve). 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 →