Critical Risk →

blender_delete_object

Delete an object from the Blender scene by name.

How to control blender_delete_object ↓

AI agents call blender_delete_object to permanently remove resources in Gamedev All-in-One MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

An AI agent that decides to call blender_delete_object doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Gamedev All-in-One MCP is gone — there is no undo for destructive operations.

Documented attack patterns abuse exactly the kind of access blender_delete_object gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and Gamedev All-in-One MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for blender_delete_object:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "blender_delete_object"
  ]
}

blender_delete_object disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register Gamedev All-in-One MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Go deeper

What does the blender_delete_object tool do? +

Delete an object from the Blender scene by name. It is categorised as a Destructive tool in the Gamedev All-in-One MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on blender_delete_object? +

Register the Gamedev All-in-One MCP server in PolicyLayer and add a rule for blender_delete_object: 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 Gamedev All-in-One MCP. Nothing to install.

What risk level is blender_delete_object? +

blender_delete_object is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit blender_delete_object? +

Yes. Add a rate_limit block to the blender_delete_object 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.

How do I block blender_delete_object completely? +

Set action: deny in the PolicyLayer policy for blender_delete_object. 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.

What MCP server provides blender_delete_object? +

blender_delete_object is provided by the Gamedev All-in-One MCP server (sansaks-jpg/gamedev-all-in-one-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Gamedev All-in-One MCP tool call.

Deterministic rules across all 78 Gamedev All-in-One MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

78 Gamedev All-in-One MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.