node_remove
A destructive tool on the Mcp Anything MCP server.
This record as markdown: /tools/mcp-anything/node-remove.md
What node_remove does on Mcp Anything
AI agents call node_remove to permanently remove resources in Mcp Anything, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why node_remove is rated Critical
The 'remove' operation implies irreversible deletion of data. While the empty description lowers confidence slightly, the naming convention and context of sibling tools (animation, camera, build systems) strongly suggests this deletes entities that cannot be easily recovered.
From the tool's definition Tool name 'node_remove' with empty description suggests irreversible deletion of a node, likely in an animation, scene graph, or build system context.
Attacks that exploit this kind of access
The rule that runs node_remove 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 node_remove, this is the rule to start with:
node_remove is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Mcp Anything, apply this rule, and every node_remove call is checked against it from then on.
Questions about node_remove
node_remove is a destructive tool on the Mcp Anything MCP server. It is categorised as a Destructive tool in the Mcp Anything MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Mcp Anything MCP server in PolicyLayer and add a rule for node_remove: 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.
node_remove is a Destructive 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 node_remove 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 node_remove. 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.
node_remove 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.
Across the catalogue