Execute arbitrary JavaScript code in the InDesign UXP context. WARNING: this runs with full InDesign DOM access and can create, modify, or destroy documents. Use only as a last resort when no other tool covers the operation.
AI agents invoke execute_indesign_code to trigger actions in InDesign UXP 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.
This tool runs arbitrary JavaScript with full DOM access inside InDesign, enabling any operation including creation, modification, and destruction of documents. It explicitly warns it can destroy documents, making it the highest-severity Execute tool — spanning Write, Destructive, and potentially other categories.
From the tool's definition "Execute arbitrary JavaScript code in the InDesign UXP context. WARNING: this runs with full InDesign DOM access and can create, modify, or destroy documents."
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 UXP MCP Server, 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 arbitrary JavaScript code in the InDesign UXP context. WARNING: this runs with full InDesign DOM access and can create, modify, or destroy documents. Use only as a last resort when no other tool covers the operation. It is categorised as a Execute tool in the InDesign UXP MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the InDesign UXP MCP Server 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 UXP MCP Server. 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 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.