photoshop_execute_script · Photoshop MCP Windows-First MCP

WHAT IT DOES

What photoshop_execute_script does on Photoshop MCP Windows-First

AI agents invoke photoshop_execute_script to trigger actions in Photoshop MCP Windows-First. 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 IT NEEDS A POLICY

Why photoshop_execute_script needs a policy

This tool executes arbitrary code (ExtendScript) in the Photoshop application context. While not inherently destructive or financial, it can perform any operation Photoshop supports—including file operations, format conversions, and potentially malicious actions. The description notes it is an 'escape hatch' with unstable output, suggesting it bypasses normal safety constraints.

From the tool's definition Tool name contains 'execute_script' and description states 'Execute arbitrary ExtendScript directly in Photoshop'. The phrase 'arbitrary ExtendScript' indicates the tool runs code with unrestricted scope.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

photoshop_execute_script Rate-limited

photoshop_execute_script 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": {
    "photoshop_execute_script": {
      "limits": [
        {
          "counter": "photoshop_execute_script_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Photoshop MCP Windows-First, so you can run agents against it safely.

FAQ

Questions about photoshop_execute_script

What does the photoshop_execute_script tool do? +

Execute arbitrary ExtendScript directly in Photoshop. Escape hatch only: output is not guaranteed to be structured or stable. It is categorised as a Execute tool in the Photoshop MCP Windows-First MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on photoshop_execute_script? +

Register the Photoshop MCP Windows-First MCP server in PolicyLayer and add a rule for photoshop_execute_script: 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 Photoshop MCP Windows-First. Nothing to install.

What risk level is photoshop_execute_script? +

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

Can I rate-limit photoshop_execute_script? +

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

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

photoshop_execute_script is provided by the Photoshop MCP Windows-First MCP server (rookietopred02-gif/photoshop-mcp-windows-first). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.