This record as markdown: /tools/mcp-anything/scene-remove.md
What scene_remove does on Mcp Anything
AI agents call scene_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 scene_remove is rated Critical
Removing a scene is a destructive action that cannot be undone. The scene and its contents are deleted from the project, representing an irreversible data loss operation. This warrants the Destructive category with high severity given the potential loss of creative work. Confidence is high based on clear intent from both the tool name and description.
From the tool's definition Tool name 'scene_remove' and description 'Remove a scene from the project' indicate irreversible deletion of project data.
Attacks that exploit this kind of access
The rule that runs scene_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 scene_remove, this is the rule to start with:
scene_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 scene_remove call is checked against it from then on.
Questions about scene_remove
Remove a scene from the project. 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 scene_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.
scene_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 scene_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 scene_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.
scene_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