Operate on Revit elements by performing actions such as select, selectionBox, setColor, setTransparency, delete, hide, etc.
AI agents call operate_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.
The tool explicitly includes 'delete' among its supported actions, which irreversibly removes Revit elements. It also includes modifications like setColor, setTransparency, and hide which are reversible (Write-level), but since delete is an option and the most severe applicable category applies, this is classified as Destructive.
From the tool's definition actions such as select, selectionBox, setColor, setTransparency, delete, hide, etc.
Attacks that exploit this kind of access
Operate on Revit elements by performing actions such as select, selectionBox, setColor, setTransparency, delete, hide, etc. 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 operate_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.
operate_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 operate_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 operate_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.
operate_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 →