image_edit_async · EFLOWCODE Image MCP: Risk & Policy

WHAT IT DOES

What image_edit_async does on EFLOWCODE Image MCP

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

WHY IT NEEDS A POLICY

Why image_edit_async needs a policy

An AI agent can call image_edit_async faster than any human can review — one bad instruction and it creates or modifies resources in EFLOWCODE Image MCP by the hundred, each call as confident as the last.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

image_edit_async Rate-limited

image_edit_async 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_edit_async": {
      "limits": [
        {
          "counter": "image_edit_async_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 EFLOWCODE Image MCP, so you can run agents against it safely.

FAQ

Questions about image_edit_async

What does the image_edit_async tool do? +

Start image-reference generation in the background and return a job_id immediately. It is categorised as a Write tool in the EFLOWCODE Image MCP 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_edit_async? +

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

What risk level is image_edit_async? +

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

Can I rate-limit image_edit_async? +

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

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

image_edit_async is provided by the EFLOWCODE Image MCP server (wenninghan/eflowcode-image-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.