save_document
A write tool on the Revit MCP server.
This record as markdown: /tools/demolinator-revit-mcp-server/save-document.md
What save_document does on Revit MCP Server
AI agents use save_document to create or update resources in Revit MCP Server, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Revit MCP Server environment.
Why save_document is rated Medium
Saving a document in Revit commits design changes, model data, and metadata to disk. This is a write operation with substantial impact—unsolicited saves could overwrite important project versions or interrupt collaborative workflows. However, it's reversible via undo/version control, so it ranks below Destructive.
From the tool's definition Tool name 'save_document' indicates it persists changes to a Revit project file. Empty description limits specificity, but the function clearly modifies persistent state by writing to the document.
Attacks that exploit this kind of access
The rule that runs save_document safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Revit MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For save_document, this is the rule to start with:
save_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.
The button opens the PolicyLayer dashboard: create your workspace, connect Revit MCP Server, apply this rule, and every save_document call is checked against it from then on.
Questions about save_document
save_document is a write tool on the Revit MCP Server MCP server. It is categorised as a Write tool in the Revit MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Revit MCP Server MCP server in PolicyLayer and add a rule for save_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 Revit MCP Server. Nothing to install.
save_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 save_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 save_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.
save_document is provided by the Revit MCP Server MCP server (demolinator/revit-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Revit MCP Server, and thousands of servers like it.
This server
Across the catalogue