AI agents call list_addons to retrieve information from Schematic without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and lists existing add-ons without modifying, deleting, or executing any operations. It is a straightforward read operation that queries data from the Schematic account.
From the tool's definition Tool name 'list_addons' and description 'List all add-ons in your Schematic account' indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
List all add-ons in your Schematic account. It is categorised as a Read tool in the Schematic MCP Server, which means it retrieves data without modifying state.
Register the Schematic MCP server in PolicyLayer and add a rule for list_addons: 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.
list_addons is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_addons 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 list_addons. 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.
list_addons 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 →