Generate an image using Krea AI. Returns a job_id - use get_job to check status and get the result URL.
AI agents invoke generate_image to trigger actions in Krea MCP Server. 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 initiates an external operation (AI image generation) on a third-party service. It is not a simple write of user data, but rather executes a compute job on an external platform. The blast radius is medium: it consumes API credits/compute resources and could generate unwanted or inappropriate content if misused, but it is not financially transactional, destructive, or irreversible in a data-loss sense.
From the tool's definition 'Generate an image using Krea AI' — triggers an external AI generation operation on Krea's infrastructure, returning a job_id for async tracking
Documented attack patterns abuse exactly the kind of access generate_image gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Krea MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for generate_image:
{
"version": "1",
"default": "deny",
"tools": {
"generate_image": {
"limits": [
{
"counter": "generate_image_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}generate_image 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.
Free to start. No card required.
Generate an image using Krea AI. Returns a job_id - use get_job to check status and get the result URL. It is categorised as a Execute tool in the Krea MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Krea MCP Server MCP server in PolicyLayer and add a rule for 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 Krea MCP Server. Nothing to install.
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 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 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.
generate_image is provided by the Krea MCP Server MCP server (keugenek/krea-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Krea MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
9 Krea MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.