object_remove
Remove an object from the scene by index.
This record as markdown: /tools/mcp-anything/object-remove.md
What object_remove does on Mcp Anything
AI agents call object_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 object_remove is rated Critical
This tool permanently deletes scene objects and cannot be undone without external undo/redo mechanisms. The irreversibility and inability to recover deleted objects places it in the Destructive category rather than Write. The severity is high because an AI agent could accidentally or maliciously remove critical scene elements, halting creative work or corrupting projects.
From the tool's definition "Remove an object from the scene by index" - the verb 'remove' combined with a specific indexing mechanism indicates irreversible deletion of scene data.
Attacks that exploit this kind of access
The rule that runs object_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 object_remove, this is the rule to start with:
object_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 object_remove call is checked against it from then on.
Questions about object_remove
Remove an object from the scene by index. 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 object_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.
object_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 object_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 object_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.
object_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