export_document
A write tool on the Revit MCP server.
This record as markdown: /tools/demolinator-revit-mcp-server/export-document.md
What export_document does on Revit MCP Server
AI agents use export_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 export_document is rated Medium
The tool exports a Revit document, which involves writing/creating output files. While export itself does not modify the original document or delete data, it creates new file artifacts and can affect downstream systems. This is Write rather than Read because it generates/commits new data outputs.
From the tool's definition Tool name 'export_document' indicates it outputs/extracts document data. No description provided. On a Revit MCP server, document export typically saves/writes data in new formats without deletion.
Attacks that exploit this kind of access
The rule that runs export_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 export_document, this is the rule to start with:
export_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 export_document call is checked against it from then on.
Questions about export_document
export_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 export_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.
export_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 export_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 export_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.
export_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