Create a new plan with a Stripe-linked billing product. This creates both the plan and its associated Stripe product and prices in one step. Prices are specified in dollars (e.g., 29.99 for $29.99/month). If no prices are provided, the plan is created with $0 pricing. Use this instead of create_p...
AI agents use create_plan_with_billing to commit financial operations through Schematic — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool directly creates billing infrastructure in Stripe, including products and prices that will be charged to customers. Misuse could result in incorrect pricing structures, unauthorized billing products, or financial obligations being committed. The Stripe integration and dollar-denominated pricing firmly place this in the Financial category.
From the tool's definition Create a new plan with a Stripe-linked billing product...creates both the plan and its associated Stripe product and prices in one step. Prices are specified in dollars (e.g., 29.99 for $29.99/month)
Attacks that exploit this kind of access
Create a new plan with a Stripe-linked billing product. This creates both the plan and its associated Stripe product and prices in one step. Prices are specified in dollars (e.g., 29.99 for $29.99/month). If no prices are provided, the plan is created with $0 pricing. Use this instead of create_plan when you want the plan to be connected to Stripe billing. It is categorised as a Financial tool in the Schematic MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Schematic MCP server in PolicyLayer and add a rule for create_plan_with_billing: 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 Schematic. Nothing to install.
create_plan_with_billing 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_plan_with_billing 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_plan_with_billing. 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_plan_with_billing is provided by the Schematic MCP server (@schematichq/schematic-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 →