illustrator_run_script_file
Illustrator: Run a script file (File > Scripts > Other Script, or a script installed in File > Scripts given by its path): .jsx, .js or .jsxbin. Like execute_illustrator_code it runs unrestricted: it can change or delete anything and read or write files. The coordinate system is left as the scrip...
This record as markdown: /tools/adobe-mcp-suite/illustrator-run-script-file.md
What illustrator_run_script_file does on Adobe Mcp Suite
AI agents invoke illustrator_run_script_file to trigger actions in Adobe Mcp Suite. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
filePath | string | Yes | Absolute .jsx, .js or .jsxbin path |
Parameters from the server's own tool schema.
Why illustrator_run_script_file is rated High
illustrator_run_script_file triggers real processes with real consequences. An agent gone sideways doesn't fire it once. It starts dozens of builds, sends mass notifications, or burns through compute before anyone looks up.
Risk signalsAccepts file system path (filePath)
Attacks that exploit this kind of access
The rule that runs illustrator_run_script_file safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Adobe Mcp Suite, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For illustrator_run_script_file, this is the rule to start with:
illustrator_run_script_file 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Adobe Mcp Suite, apply this rule, and every illustrator_run_script_file call is checked against it from then on.
Questions about illustrator_run_script_file
Illustrator: Run a script file (File > Scripts > Other Script, or a script installed in File > Scripts given by its path): .jsx, .js or .jsxbin. Like execute_illustrator_code it runs unrestricted: it can change or delete anything and read or write files. The coordinate system is left as the script expects; Illustrator's own alerts are suppressed while it runs. A script that opens its own dialog waits for the user. Returns the script's last value as text. The file must be inside the allowed folders (add Illustrator's Scripts folder to ILLUSTRATOR_ALLOWED_DIRS to run installed scripts). It is categorised as a Execute tool in the Adobe Mcp Suite MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
illustrator_run_script_file accepts 1 parameter: filePath. Required: filePath. The full parameter table on this page comes from the server's own tool schema.
Register the Adobe Mcp Suite MCP server in PolicyLayer and add a rule for illustrator_run_script_file: 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 Adobe Mcp Suite. Nothing to install.
illustrator_run_script_file 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 illustrator_run_script_file 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 illustrator_run_script_file. 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.
illustrator_run_script_file is provided by the Adobe Mcp Suite MCP server (adobe-mcp-suite). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Adobe Mcp Suite, and thousands of servers like it.
Across the catalogue