image_process_local · TSCodex MCP Images MCP: Risk & Policy

WHAT IT DOES

What image_process_local does on TSCodex MCP Images

AI agents use image_process_local to create or update resources in TSCodex MCP Images — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your TSCodex MCP Images environment.

WHY IT NEEDS A POLICY

Why image_process_local needs a policy

The tool modifies image files (resize, crop, format conversion, optimization) but these are all reversible Write operations. The user retains the original file and can revert changes. There is no irreversible deletion (Destructive), code execution (Execute), financial transaction (Financial), or side effects beyond the intended image transformation.

From the tool's definition Tool description states it performs 'resize, crop, convert format, optimize' on local image files. These are reversible modifications that create or alter image data without deleting the original.

Risk signalsAdmin/system-level operation

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

image_process_local Rate-limited

image_process_local stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "image_process_local": {
      "limits": [
        {
          "counter": "image_process_local_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about image_process_local

What does the image_process_local tool do? +

Process local image file: resize, crop, convert format, optimize. All paths are relative to the project root. It is categorised as a Write tool in the TSCodex MCP Images MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on image_process_local? +

Register the TSCodex MCP Images MCP server in PolicyLayer and add a rule for image_process_local: 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 TSCodex MCP Images. Nothing to install.

What risk level is image_process_local? +

image_process_local is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit image_process_local? +

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

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

image_process_local is provided by the TSCodex MCP Images MCP server (unbywyd/tscodex-mcp-images). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.