文本生成图像。provider 可用 gpt/GPT/openai、grok/xai、banana/nano/nano-banana。
AI agents use image_generate 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_generate 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
文本生成图像。provider 可用 gpt/GPT/openai、grok/xai、banana/nano/nano-banana。. 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_generate: 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_generate 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_generate 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_generate. 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_generate 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.