AI agents use create_addon to create or update resources in Schematic — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Schematic environment.
This tool creates new add-on records, which is a reversible write operation. It modifies system state by adding new data but does not delete, execute arbitrary code, or move money. Severity is medium because misuse could create unwanted billing records, but the operation is reversible and doesn't directly impact financial transactions or destroy data.
From the tool's definition Tool name 'create_addon' and description 'Create a new add-on' indicate data creation operation. Context of sibling tools (create_company, create_plan, create_plan_with_billing) confirms this is a write operation in a billing/subscription management system.
Attacks that exploit this kind of access
Create a new add-on. It is categorised as a Write tool in the Schematic MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Schematic MCP server in PolicyLayer and add a rule for create_addon: 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_addon 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 create_addon 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_addon. 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_addon 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 →