Send C# code to Revit for execution. The code will be inserted into a template with access to the Revit Document and parameters. Your code should be written to work within the Execute method of the template.
AI agents invoke send_code_to_revit to trigger actions in Revit. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool executes arbitrary user-supplied C# code within Revit, giving full programmatic access to the BIM model. An AI agent could run any code including destructive operations (delete elements, modify structure), data exfiltration, or other unintended side effects. The blast radius is critical because there are no apparent sandboxing constraints mentioned, and the code runs with full Revit Document access.
From the tool's definition "Send C# code to Revit for execution" — arbitrary C# code is executed inside Revit's environment with access to the Document and parameters
Attacks that exploit this kind of access
Send C# code to Revit for execution. The code will be inserted into a template with access to the Revit Document and parameters. Your code should be written to work within the Execute method of the template. It is categorised as a Execute tool in the Revit MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Revit MCP server in PolicyLayer and add a rule for send_code_to_revit: 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.
send_code_to_revit is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the send_code_to_revit 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 send_code_to_revit. 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.
send_code_to_revit 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 →