Critical Risk →

delete_entities_by_handles

Delete multiple entities by their handles

How to control delete_entities_by_handles ↓

AI agents call delete_entities_by_handles to permanently remove resources in AutoCAD MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

This tool irreversibly deletes CAD entities from the AutoCAD drawing. Deletion cannot be undone programmatically through the MCP interface and represents permanent loss of design work. While severity is high rather than critical because AutoCAD itself may have undo capabilities, the MCP operation itself is destructive.

From the tool's definition Tool name is 'delete_entities_by_handles' and description states 'Delete multiple entities by their handles'. The verb 'delete' and context of CAD entities indicate irreversible removal of data.

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

PolicyLayer is an MCP gateway — it sits between your AI agents and AutoCAD MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for delete_entities_by_handles:

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

delete_entities_by_handles 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 AutoCAD MCP Server — 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 delete_entities_by_handles tool do? +

Delete multiple entities by their handles. It is categorised as a Destructive tool in the AutoCAD MCP Server 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 delete_entities_by_handles? +

Register the AutoCAD MCP Server MCP server in PolicyLayer and add a rule for delete_entities_by_handles: 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 AutoCAD MCP Server. Nothing to install.

What risk level is delete_entities_by_handles? +

delete_entities_by_handles 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 delete_entities_by_handles? +

Yes. Add a rate_limit block to the delete_entities_by_handles 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 delete_entities_by_handles completely? +

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

delete_entities_by_handles is provided by the AutoCAD MCP Server MCP server (thepiruthvirajan/autocad-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every AutoCAD MCP Server tool call.

Deterministic rules across all 21 AutoCAD MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

21 AutoCAD MCP Server 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.