Generate an image using the configured provider.
AI agents invoke kilo_generate_image to trigger actions in Jgkme/kilo Image Gen. 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.
This tool triggers an external operation (image generation) via a configured provider (Kilo, OpenRouter, OpenAI, or Gemini). It executes an API call to an external service, which may incur costs and produces side effects (image creation). It's Execute rather than Write because it runs an operation on an external provider whose behavior depends on arguments.
From the tool's definition Generate an image using the configured provider
Attacks that exploit this kind of access
Generate an image using the configured provider. It is categorised as a Execute tool in the Jgkme/kilo Image Gen MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Jgkme/kilo Image Gen MCP server in PolicyLayer and add a rule for kilo_generate_image: 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 Jgkme/kilo Image Gen. Nothing to install.
kilo_generate_image 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 kilo_generate_image 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 kilo_generate_image. 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.
kilo_generate_image is provided by the Jgkme/kilo Image Gen MCP server (jgkme/img-gen-mcp). 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 →