operate_element

THE RISK

Critical Risk

Why operate_element needs a policy

Although operate_element supports multiple action types including reversible ones (select, setColor, setTransparency, hide), the inclusion of 'delete' as a capability elevates this to Destructive category. In architectural/BIM contexts, deleting elements from a Revit project permanently removes geometry, annotations, and associated data that cannot be recovered without undo/version control.

From the tool's definition Tool description explicitly lists 'delete' as an action that can be performed on Revit elements. The delete action is irreversible and destroys architectural model data.

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

POLICY

How to control operate_element

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

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "operate_element"
  ]
}

operate_element disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register Revit MCP — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Revit MCP tools

Destructive delete_element Delete one or more elements from the Revit model by their element IDs. Execute say_hello Display a greeting dialog in Revit. Useful for testing the connection between Claude and R Execute send_code_to_revit Send C code to Revit for execution. The code will be inserted into a template with access Write color_elements Color elements in the current view based on a category and parameter value. Each unique pa Write store_project_data Store or update Revit project metadata in the local database. This captures project inform Write store_room_data Store or update room metadata for a specific Revit project in the local database. Rooms ar Write create_grid Create a grid system in Revit with smart spacing generation. Supports both X-axis (vertica Write create_level Create one or more levels in Revit at specified elevations. Levels define horizontal plane

All 25 Revit MCP tools →

Destructive tools on other servers

Android Forensics ADB MCP Server create_full_backup 0xarchive web3_revoke_key Frida Game Hacking MCP clear_scan cPanel MCP Server clear_spam_box

Go deeper

Critical-risk tools in Revit MCP → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Blast radius → How much damage one compromised or confused agent can do — and how to bound it.
Tool call approval → Approval gates on individual tool calls: auto-allow, prompt, or deny.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about operate_element

What does the operate_element tool do? +

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

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 MCP. Nothing to install.

What risk level is operate_element? +

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

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.

How do I block operate_element completely? +

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.

What MCP server provides operate_element? +

operate_element is provided by the Revit MCP server (mcp-servers-for-revit/revit-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Revit MCP tool call.

Start from Revit MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →