AI agents use export_document_xml to create or update resources in InDesign UXP MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your InDesign UXP MCP Server environment.
This tool creates a new output file (the XML export) derived from the current document state. While it does not modify the original InDesign document, it writes/generates new data as an export artifact. This is a Write operation rather than Read (which would only retrieve data without generating files) or Destructive (no data is deleted or overwritten in the primary document).
From the tool's definition export_document_xml: Export document as XML. Exports the document in a non-native format (XML), which writes/serializes the document data to a new file or output stream.
Documented attack patterns abuse exactly the kind of access export_document_xml gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and InDesign UXP MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for export_document_xml:
{
"version": "1",
"default": "deny",
"tools": {
"export_document_xml": {
"limits": [
{
"counter": "export_document_xml_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}export_document_xml 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.
Export document as XML. It is categorised as a Write tool in the InDesign UXP MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the InDesign UXP MCP Server MCP server in PolicyLayer and add a rule for export_document_xml: 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 InDesign UXP MCP Server. Nothing to install.
export_document_xml 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_xml 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_xml. 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_xml is provided by the InDesign UXP MCP Server MCP server (theloniuser/indesign-uxp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 135 InDesign UXP MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
135 InDesign UXP MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.