Open a Revit document file in the running Revit instance. Supports workshared (central) files with options to detach from central or audit the file on open. Args: file_path: Absolute path to a .rvt, .rfa, or .rte file. detach: If True, open detached from central (workshared files only). Preserves...
AI agents use open_document to create or update resources in MCP server for Revit - Python — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP server for Revit - Python environment.
Opening a document in Revit changes the current working state and active model context of the application. While not destructive (the original file is preserved), this is a Write operation because it modifies the active state and can affect worksets and model relationships (detach from central).
From the tool's definition Tool opens a Revit document file and modifies the state of the running Revit instance. Description states it 'Open a Revit document file in the running Revit instance' with options to 'detach from central' or 'audit the file', which are state-changing…
Documented attack patterns abuse exactly the kind of access open_document gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP server for Revit - Python, and nothing reaches the server without passing your rules. This is the rule we recommend for open_document:
{
"version": "1",
"default": "deny",
"tools": {
"open_document": {
"limits": [
{
"counter": "open_document_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}open_document stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Open a Revit document file in the running Revit instance. Supports workshared (central) files with options to detach from central or audit the file on open. Args: file_path: Absolute path to a .rvt, .rfa, or .rte file. detach: If True, open detached from central (workshared files only). Preserves worksets but severs the link to the central model. audit: If True, audit the file on open to check for corruption. It is categorised as a Write tool in the MCP server for Revit - Python MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP server for Revit - Python MCP server in PolicyLayer and add a rule for open_document: 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 MCP server for Revit - Python. Nothing to install.
open_document is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the open_document 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 open_document. 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.
open_document is provided by the MCP server for Revit - Python MCP server (mcp-servers-for-revit/mcp-server-for-revit-python). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP server for Revit - Python, 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.
20 MCP server for Revit - Python tools catalogued and risk-classified — across an index of 43,000+ MCP servers.