Generate AI images based on a text description. Returns an image file.
AI agents invoke image_generation to trigger actions in Deerflow Kinthai. 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.
The tool triggers an external AI image generation operation based on user-provided text input. This is an external computation/generation action whose output depends on arguments, fitting the Execute category. It does not merely read existing data, nor does it write to a user-controlled data store in a reversible way — it invokes an AI model pipeline.
From the tool's definition 'Generate AI images based on a text description. Returns an image file.'
Attacks that exploit this kind of access
Generate AI images based on a text description. Returns an image file. It is categorised as a Execute tool in the Deerflow Kinthai MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Deerflow Kinthai MCP server in PolicyLayer and add a rule for image_generation: 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 Deerflow Kinthai. Nothing to install.
image_generation is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the image_generation 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_generation. 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_generation is provided by the Deerflow Kinthai MCP server (kinthaiofficial/mcp-server-deerflow-kinthai). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →