Generate an image from text (optionally edit an existing one).
AI agents invoke generate_image to trigger actions in AgentSpawnMCP. 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 executes an external API call to generate or edit images. It is not a simple read, nor does it destroy data or move money. It triggers an external operation (image generation/editing) whose output depends on the input arguments, placing it in the Execute category. Misuse could incur API costs or produce harmful imagery, warranting medium severity.
From the tool's definition "Generate an image from text (optionally edit an existing one)" — triggers an external image generation operation via an OpenAI-compatible LLM API
Attacks that exploit this kind of access
Generate an image from text (optionally edit an existing one). It is categorised as a Execute tool in the AgentSpawnMCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the AgentSpawn 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 AgentSpawnMCP. 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 AgentSpawn MCP server (sandsaber/agentspawnmcp). 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 →