AI agents call delete_pattern to permanently remove resources in CLO3D 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 pattern pieces from a CLO3D project. Pattern pieces represent design work that has been created in the project. Deletion is irreversible and constitutes data destruction. While the blast radius is limited to a single pattern (not the entire project), the loss of work is permanent and could impact design iterations.
From the tool's definition Tool name 'delete_pattern' and description 'Delete a pattern piece from the project' explicitly indicate irreversible deletion of data. The verb 'delete' is a destructive operation that cannot be undone.
Documented attack patterns abuse exactly the kind of access delete_pattern gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and CLO3D MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_pattern:
{
"version": "1",
"default": "deny",
"hide": [
"delete_pattern"
]
} delete_pattern 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 a pattern piece from the project. It is categorised as a Destructive tool in the CLO3D MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the CLO3D MCP Server MCP server in PolicyLayer and add a rule for delete_pattern: 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 CLO3D MCP Server. Nothing to install.
delete_pattern 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_pattern 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_pattern. 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_pattern is provided by the CLO3D MCP Server MCP server (ubani-studio/clo3d-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from CLO3D MCP Server, 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.
33 CLO3D MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.