AI agents use create_checkout to commit financial operations through Run402 — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool initiates a Stripe checkout session, which is directly tied to financial transactions — purchasing balance top-ups, subscription tiers, or email packs. Even though it creates a URL rather than directly charging, it commits the organization to a financial flow and can result in real monetary charges if completed. This clearly falls under the Financial category, which is the most severe applicable.
From the tool's definition 'Create a Stripe checkout URL for an organization. Products: balance_topup, tier, email_pack.'
Attacks that exploit this kind of access
Create a Stripe checkout URL for an organization. Products: balance_topup, tier, email_pack. It is categorised as a Financial tool in the Run402 MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Run402 MCP server in PolicyLayer and add a rule for create_checkout: 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 Run402. Nothing to install.
create_checkout 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 create_checkout 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 create_checkout. 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.
create_checkout is provided by the Run402 MCP server (kychee-com/run402). 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 →