批量单图编辑。对每张图片独立调用 image_edit,provider 参数会透传。
AI agents use image_batch_edit 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.
An AI agent can call image_batch_edit 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
批量单图编辑。对每张图片独立调用 image_edit,provider 参数会透传。. 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.
Register the EFLOWCODE Image MCP server in PolicyLayer and add a rule for image_batch_edit: 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.
image_batch_edit is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the image_batch_edit 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 image_batch_edit. 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.
image_batch_edit 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.