AI agents invoke open_document to trigger actions in InDesign MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Opening a document in InDesign is not a pure read/query operation; it executes an action within the InDesign application, loading a file into the environment and changing application state. It does not delete or modify data, but it does trigger an external operation whose effects (e.g., file locks, script execution on open, resource consumption) depend on the document being opened.
From the tool's definition 'Open an existing document' — triggers an external operation in Adobe InDesign to open a file, causing a side effect in the application state.
Documented attack patterns abuse exactly the kind of access open_document gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and InDesign MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for open_document:
{
"version": "1",
"default": "deny",
"tools": {
"open_document": {
"limits": [
{
"counter": "open_document_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}open_document stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Open an existing document. It is categorised as a Execute tool in the InDesign MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the InDesign MCP Server MCP server in PolicyLayer and add a rule for open_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 MCP Server. Nothing to install.
open_document is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the open_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 open_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.
open_document is provided by the InDesign MCP Server MCP server (zachshallbetter/indesign-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from InDesign MCP Server, 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.
135 InDesign MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.