AI agents call export_images to retrieve information from Indesign without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Exporting pages as images reads the document content and writes output files to disk, but does not modify the source document. The primary action is reading/rendering existing content. Severity is low since the worst case is creating image files in an unintended location.
From the tool's definition Export pages as images
Documented attack patterns abuse exactly the kind of access export_images 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 export_images:
{
"version": "1",
"default": "deny",
"tools": {
"export_images": {}
}
}export_images is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Export pages as images. It is categorised as a Read tool in the Indesign MCP Server, which means it retrieves data without modifying state.
Register the Indesign MCP server in PolicyLayer and add a rule for export_images: 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.
export_images is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the export_images 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_images. 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_images 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.