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 MCP. 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 C# code inside Revit with full access to the Revit Document. An AI agent could use this to perform any operation — reading, writing, deleting elements, modifying project data, or even interacting with the file system — making it extremely high risk. Arbitrary code execution with document-level access is the definition of critical severity under the Execute category.
From the tool's definition Send C# code to Revit for execution. The code will be inserted into a template with access to the Revit Document and parameters.
Documented attack patterns abuse exactly the kind of access send_code_to_revit gives an agent:
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 send_code_to_revit:
{
"version": "1",
"default": "deny",
"tools": {
"send_code_to_revit": {
"limits": [
{
"counter": "send_code_to_revit_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}send_code_to_revit stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
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 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 MCP. 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 (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.
Start from Revit MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
25 Revit MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.