Package document for print production
AI agents use package_document to create or update resources in Indesign — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Indesign environment.
Packaging a document for print production creates new files or modifies the document state in a way that prepares it for external use. This is reversible (the original document remains intact, and the package can be regenerated or deleted), making it a Write rather than Destructive action. It does not execute arbitrary code, delete data irreversibly, or move money.
From the tool's definition Tool name 'package_document' with description 'Package document for print production' indicates creation of a packaged output file/artifact for production purposes. This is a write operation that creates or modifies deliverable outputs.
Documented attack patterns abuse exactly the kind of access package_document gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Indesign, and nothing reaches the server without passing your rules. This is the rule we recommend for package_document:
{
"version": "1",
"default": "deny",
"tools": {
"package_document": {
"limits": [
{
"counter": "package_document_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}package_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.
Package document for print production. It is categorised as a Write tool in the Indesign MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Indesign MCP server in PolicyLayer and add a rule for package_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. Nothing to install.
package_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 package_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 package_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.
package_document is provided by the Indesign MCP server (lucdesign/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, 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.
36 Indesign tools catalogued and risk-classified — across an index of 43,000+ MCP servers.