Delete an object from the Blender scene. Parameters: - name: Name of the object to delete
AI agents call delete_object to permanently remove resources in Tripo MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes data (3D objects) from a Blender scene. Deletion is irreversible and constitutes a destructive action. While the blast radius is somewhat contained to a single Blender project (rather than system-wide or financial), an AI agent with unchecked access could maliciously delete valuable 3D assets that took significant effort to create.
From the tool's definition Tool name is 'delete_object' with description 'Delete an object from the Blender scene.' The verb 'delete' is irreversible—once an object is removed from the scene, it cannot be automatically recovered without undo functionality being externally managed.
Documented attack patterns abuse exactly the kind of access delete_object gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Tripo MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_object:
{
"version": "1",
"default": "deny",
"hide": [
"delete_object"
]
} 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.
Free to start. No card required.
Delete an object from the Blender scene. Parameters: - name: Name of the object to delete. It is categorised as a Destructive tool in the Tripo MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Tripo MCP Server MCP server in PolicyLayer and add a rule for 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 Tripo MCP Server. Nothing to install.
delete_object 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 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.
Set action: deny in the PolicyLayer policy for 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.
delete_object is provided by the Tripo MCP Server MCP server (vast-ai-research/tripo-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 16 Tripo MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
16 Tripo MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.