Close the active Revit document. Args: save: If True, save the document before closing. If False (default), close without saving.
AI agents call close_document to permanently remove resources in MCP server for Revit - Python — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Closing a document without saving permanently discards any unsaved work. Even with save=True, the action of closing the active document is irreversible in terms of the working session. The default behavior (save=False) means unsaved changes are lost permanently, making this Destructive. High severity because an AI agent misusing this could cause loss of significant engineering/design work in a Revit model.
From the tool's definition 'Close the active Revit document' with 'If False (default), close without saving' — default behavior discards unsaved changes irreversibly
Documented attack patterns abuse exactly the kind of access close_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 close_document:
{
"version": "1",
"default": "deny",
"hide": [
"close_document"
]
} close_document disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Close the active Revit document. Args: save: If True, save the document before closing. If False (default), close without saving. It is categorised as a Destructive tool in the MCP server for Revit - Python MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MCP server for Revit - Python MCP server in PolicyLayer and add a rule for close_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.
close_document 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 close_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 close_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.
close_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.