Delete one or more elements from the Revit model by their element IDs.
AI agents call delete_element to permanently remove resources in Revit — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes elements from a Revit project, which cannot be undone except through undo/redo operations. The deletion is irreversible in the model state, affecting project integrity. While not inherently financial, the blast radius is high because an AI agent could accidentally or maliciously delete critical building components, structural elements, or entire sections of a design.
From the tool's definition Tool name is 'delete_element' and description states 'Delete one or more elements from the Revit model by their element IDs.' The verb 'delete' and the irreversible nature of removing elements from a BIM model are explicit.
Attacks that exploit this kind of access
Delete one or more elements from the Revit model by their element IDs. It is categorised as a Destructive tool in the Revit MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Revit MCP server in PolicyLayer and add a rule for delete_element: 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 Revit. Nothing to install.
delete_element 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_element 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_element. 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_element is provided by the Revit MCP server (mohamed-elnahla/revit-mcp-github-copilot). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →