illustrator_run_batch

SERVERAdobe Mcp Suite SOURCEadobe-mcp-suite

High RISK CLASS

Category Execute

Parameters 112 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/adobe-mcp-suite/illustrator-run-batch.md

WHAT IT DOES

What illustrator_run_batch does on Adobe Mcp Suite

AI agents invoke illustrator_run_batch 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
`set`	string	Yes	Action set name (Batch > Set)
`action`	string	Yes	Action name (Batch > Action)
`source`	string	—	Batch > Source. Default folder
`onError`	string	—	stop at the first error (default) or carry on and list the errors
`maxFiles`	integer	—	Refuse a folder with more matching files than this. Default 200
`fileTypes`	array	—	File extensions to open. Default ai, pdf, eps and svg
`fileNaming`	string	—	Data sets to a folder: file_number (document name + 001), file_data_set (document name_data set name, default), data_set (data set name)
`destination`	string	—	Batch > Destination: none (leave open), save_and_close, folder. Default none
`sourceFolder`	string	—	Absolute folder path, for source folder
`destinationFolder`	string	—	Absolute folder path, for destination folder
`includeSubfolders`	boolean	—	Include All Subdirectories. Default false

Parameters from the server's own tool schema.

RISK

Why illustrator_run_batch is rated High

illustrator_run_batch 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 (destination) · High parameter count (11 properties) · Bulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs illustrator_run_batch 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_batch, this is the rule to start with:

illustrator_run_batch Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "illustrator_run_batch": {
      "limits": [
        {
          "counter": "illustrator_run_batch_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Adobe Mcp Suite, apply this rule, and every illustrator_run_batch call is checked against it from then on.

FAQ

Questions about illustrator_run_batch

What does the illustrator_run_batch tool do? +

Illustrator: Play an action on every file in a folder, or on every data set of the active document, and save the results (does what Actions panel > Batch does, by script). Folder: each .ai, .pdf, .eps or .svg file is opened, the action played, and the file left open (destination none), saved in place and closed (save_and_close), or saved as an .ai copy in destinationFolder and closed (folder; subfolders are recreated). Files already open are skipped with an error. Data sets: each data set is displayed, the action played, and with destination folder the document saved as an .ai file named by fileNaming; the document then refers to the last file saved. Save and Export steps inside the action still run as recorded. Each file runs as its own call, so a long batch does not time out. 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.

What parameters does illustrator_run_batch accept? +

illustrator_run_batch accepts 11 parameters: set, action, source, onError, maxFiles, fileTypes, fileNaming, destination, sourceFolder, destinationFolder, includeSubfolders. Required: set, action. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on illustrator_run_batch? +

Register the Adobe Mcp Suite MCP server in PolicyLayer and add a rule for illustrator_run_batch: 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.

What risk level is illustrator_run_batch? +

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

Can I rate-limit illustrator_run_batch? +

Yes. Add a rate_limit block to the illustrator_run_batch 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 illustrator_run_batch completely? +

Set action: deny in the PolicyLayer policy for illustrator_run_batch. 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 illustrator_run_batch? +

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

KEEP EXPLORING

More on Adobe Mcp Suite, and thousands of servers like it.

This server

All 447 Adobe Mcp Suite tools → High-risk tools on this server →

Across the catalogue

editor_run_template on 010 Editor →run on 0sec →shortcuts_run on Apple Apps MCP →run_emba_scan on EMBA-MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →