AI agents use save_document 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 modifies the document state by writing it to storage, making it a Write action. While reversible (the previous version may exist in file history), it commits changes and could overwrite prior document states. Severity is medium because the impact is limited to the active document and the user presumably intends to save; misuse by an agent could however discard recent work by saving an unwanted state.
From the tool's definition Tool name 'save_document' and description 'Save the active document' indicate a file-write operation that persists data to disk.
Documented attack patterns abuse exactly the kind of access save_document 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 save_document:
{
"version": "1",
"default": "deny",
"tools": {
"save_document": {
"limits": [
{
"counter": "save_document_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}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.
Free to start. No card required.
Save the active document. 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 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 InDesign UXP 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 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.