run_image_command
Run an Object menu image command on the targets: remove_background (Object > Remove Background, Illustrator 30.4 and later: keeps the subject of an image), make_mockup (Object > Mockup > Make / Preview: wrap the vector art onto the image beneath it; select both), release_mockup (Object > Mockup >...
This record as markdown: /tools/adobe-mcp-illustrator/run-image-command.md
What run_image_command does on Adobe Mcp Illustrator
AI agents invoke run_image_command 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_image_command is rated High
run_image_command 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_image_command 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_image_command, this is the rule to start with:
run_image_command 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_image_command call is checked against it from then on.
Questions about run_image_command
Run an Object menu image command on the targets: remove_background (Object > Remove Background, Illustrator 30.4 and later: keeps the subject of an image), make_mockup (Object > Mockup > Make / Preview: wrap the vector art onto the image beneath it; select both), release_mockup (Object > Mockup > Release). These features may download components or contact Adobe services on first use, so a call can take a while. 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_image_command: 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_image_command 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_image_command 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_image_command. 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_image_command 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