component_add
A write tool on the Mcp Anything MCP server.
This record as markdown: /tools/mcp-anything/component-add.md
What component_add does on Mcp Anything
AI agents use component_add to create or update resources in Mcp Anything, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Mcp Anything environment.
Why component_add is rated Medium
Without a description, classification relies on naming convention and context from sibling tools. 'component_add' most likely creates a new component (a reversible Write operation) rather than executing arbitrary code or destroying data. The medium severity reflects typical component creation risks—incorrect additions could impact project state but remain reversible. Confidence is moderate due to missing description.
From the tool's definition Tool name 'component_add' indicates creation of a new component. The 'add' verb suggests a write operation that creates or modifies data.
Attacks that exploit this kind of access
The rule that runs component_add safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp Anything, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For component_add, this is the rule to start with:
component_add stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Anything, apply this rule, and every component_add call is checked against it from then on.
Questions about component_add
component_add is a write tool on the Mcp Anything MCP server. It is categorised as a Write tool in the Mcp Anything MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Mcp Anything MCP server in PolicyLayer and add a rule for component_add: 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 Mcp Anything. Nothing to install.
component_add 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 component_add 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 component_add. 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.
component_add is provided by the Mcp Anything MCP server (Zaymadkid/mcp-anything). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Mcp Anything, and thousands of servers like it.
This server
Across the catalogue