AI agents invoke generate_ai_image to trigger actions in Portals. 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
prompt | string | Yes | Text description of the image to generate. |
spaceId | string | — | Space/room ID to associate the image with. Defaults to the current room. |
Parameters from the server's own tool schema.
This tool triggers an external computation (AI image generation via Google Imagen 4 Fast through Replicate), which constitutes executing an external operation whose effects depend on arguments. It's not a simple read/write — it initiates an async process on a third-party service. Severity is medium because misuse could incur API costs and generate unwanted content, but it doesn't directly delete data or move money.
From the tool's definition Generate an AI image from a text prompt... Kicks off an async job
Attacks that exploit this kind of access
Generate an AI image from a text prompt using Google Imagen 4 Fast (via Replicate). Kicks off an async job — poll list_generated_images until the new item has a populated image URL. It is categorised as a Execute tool in the Portals MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
generate_ai_image accepts 2 parameters: prompt, spaceId. Required: prompt. The full parameter table on this page comes from the server's own tool schema.
Register the Portals MCP server in PolicyLayer and add a rule for generate_ai_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 Portals. Nothing to install.
generate_ai_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_ai_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_ai_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_ai_image is provided by the Portals MCP server (portals-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 →