Delete one or more objects from the Rhino document.
AI agents call delete_objects to permanently remove resources in GOLEM-3DMCP-Rhino- — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Deletion of objects in a Rhino document cannot be undone programmatically through the MCP interface and represents permanent data loss. While Rhino itself has an undo feature, an AI agent invoking this tool in error would cause immediate loss of user work. This fits the Destructive category definition: irreversibly deletes data.
From the tool's definition Tool name is "delete_objects" and description states it will "Delete one or more objects from the Rhino document." This is an irreversible operation that removes data permanently.
Documented attack patterns abuse exactly the kind of access delete_objects gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and GOLEM-3DMCP-Rhino-, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_objects:
{
"version": "1",
"default": "deny",
"hide": [
"delete_objects"
]
}delete_objects 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 one or more objects from the Rhino document. It is categorised as a Destructive tool in the GOLEM-3DMCP-Rhino- MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the GOLEM-3DMCP-Rhino- MCP server in PolicyLayer and add a rule for delete_objects: 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 GOLEM-3DMCP-Rhino-. Nothing to install.
delete_objects 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_objects 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_objects. 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_objects is provided by the GOLEM-3DMCP-Rhino- MCP server (thekinghippopotamus/golem-3dmcp-rhino-). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from GOLEM-3DMCP-Rhino-, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
89 GOLEM-3DMCP-Rhino- tools catalogued and risk-classified — across an index of 43,000+ MCP servers.