Execute custom ExtendScript code in InDesign
AI agents invoke execute_indesign_code to trigger actions in Indesign. 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.
This tool allows running arbitrary ExtendScript (JavaScript-based scripting language for Adobe applications) within InDesign. ExtendScript has access to InDesign's object model and can perform a wide range of operations including document manipulation, file I/O, and external process invocation. The effects are dependent on the code arguments provided, making this an Execute risk.
From the tool's definition Tool name 'execute_indesign_code' and description 'Execute custom ExtendScript code in InDesign' directly indicate arbitrary code execution capabilities within the InDesign application environment.
Documented attack patterns abuse exactly the kind of access execute_indesign_code 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 execute_indesign_code:
{
"version": "1",
"default": "deny",
"tools": {
"execute_indesign_code": {
"limits": [
{
"counter": "execute_indesign_code_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
} execute_indesign_code 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.
Execute custom ExtendScript code in InDesign. It is categorised as a Execute tool in the Indesign MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Indesign MCP server in PolicyLayer and add a rule for execute_indesign_code: 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.
execute_indesign_code 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 execute_indesign_code 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 execute_indesign_code. 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.
execute_indesign_code 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.