image_multi_reference_async · EFLOWCODE Image MCP

WHAT IT DOES

What image_multi_reference_async does on EFLOWCODE Image MCP

AI agents invoke image_multi_reference_async to trigger actions in EFLOWCODE Image MCP. 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 image_multi_reference_async needs a policy

image_multi_reference_async 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

Recommended rule Ready

Verdict

image_multi_reference_async Rate-limited

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

FAQ

Questions about image_multi_reference_async

What does the image_multi_reference_async tool do? +

Start multi-reference image generation in the background and return a job_id immediately. It is categorised as a Execute tool in the EFLOWCODE Image MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on image_multi_reference_async? +

Register the EFLOWCODE Image MCP server in PolicyLayer and add a rule for image_multi_reference_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_multi_reference_async? +

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

Can I rate-limit image_multi_reference_async? +

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

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

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