execute_indesign_code

THE RISK

High Risk

Why execute_indesign_code needs a policy

This tool permits execution of arbitrary code within the InDesign application context. While the blast radius is limited to InDesign (not system-level shell execution), it can modify documents, access file systems, and perform irreversible operations depending on the injected script. An AI agent with malicious or misguided prompts could execute destructive ExtendScript.

From the tool's definition Tool name is 'execute_indesign_code' and description states 'Execute custom InDesign ExtendScript code'. The verb 'Execute' combined with 'custom' code capability indicates this runs arbitrary ExtendScript, which is a programming language for Adobe InDesign.

Documented attack patterns abuse exactly the kind of access execute_indesign_code gives an agent:

POLICY

How to control execute_indesign_code

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 execute_indesign_code:

policy.json

{
  "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.

Create a free account and register InDesign MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More InDesign MCP Server tools

Destructive cleanup_document Clean up document (remove unused elements) Destructive clear_session Clear all session data including page dimensions and document information Destructive delete_all_page_layout_snapshots Delete all layout snapshots for a page Destructive delete_master_spread Delete a master spread Destructive delete_page Delete a page from the document Destructive delete_page_item Delete a page item Destructive delete_page_layout_snapshot Delete the layout snapshot for a page Destructive delete_spread Delete a spread

All 135 InDesign MCP Server tools →

Execute tools on other servers

Android Forensics ADB MCP Server adb_shell_command EMBA-MCP run_emba_scan Frida Game Hacking MCP remove_breakpoint Procmon request_elevation

Go deeper

High-risk tools in InDesign MCP Server → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Agent sandbox → Bounding what an agent can execute and where the boundary should sit.
Least privilege for MCP → Granting agents the minimum tool surface the task needs.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about execute_indesign_code

What does the execute_indesign_code tool do? +

Execute custom InDesign ExtendScript code. 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.

How do I enforce a policy on execute_indesign_code? +

Register the InDesign 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 MCP Server. Nothing to install.

What risk level is execute_indesign_code? +

execute_indesign_code is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit execute_indesign_code? +

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.

How do I block execute_indesign_code completely? +

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.

What MCP server provides execute_indesign_code? +

execute_indesign_code 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.

Enforce policy on every InDesign MCP Server tool call.

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.

CHECK YOUR STACK →