AI agents use add_entitlements_to_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 or modifies entitlements associated with an add-on product, which is a reversible write operation. The high severity reflects that modifying entitlements could affect customer access and billing relationships, creating potential business impact if misused by an agent.
From the tool's definition Tool name contains 'add' and description states 'Add entitlements to an add-on', indicating a modification operation. The incomplete description cuts off mid-sentence but clearly indicates data modification rather than deletion or financial transaction.
Attacks that exploit this kind of access
Add entitlements to an add-on. The feature type will be automatically determined by querying the feature. For boolean features, defaults to. 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 add_entitlements_to_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.
add_entitlements_to_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 add_entitlements_to_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 add_entitlements_to_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.
add_entitlements_to_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 →