run_script_file
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; Il...
This record as markdown: /tools/adobe-mcp-illustrator/run-script-file.md
What run_script_file does on Adobe Mcp Illustrator
AI agents invoke run_script_file to trigger actions in Adobe Mcp Illustrator. 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.
Why run_script_file is rated High
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.
Attacks that exploit this kind of access
The rule that runs run_script_file safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Adobe Mcp Illustrator, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For run_script_file, this is the rule to start with:
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 Illustrator, apply this rule, and every run_script_file call is checked against it from then on.
Questions about run_script_file
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\. It is categorised as a Execute tool in the Adobe Mcp Illustrator MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Adobe Mcp Illustrator MCP server in PolicyLayer and add a rule for 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 Illustrator. Nothing to install.
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 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 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.
run_script_file is provided by the Adobe Mcp Illustrator MCP server (adobe-mcp-illustrator). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Adobe Mcp Illustrator, and thousands of servers like it.
Across the catalogue