AI agents invoke generate_ai_texture 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 texture (e.g. 'mossy stone wall', 'polished oak planks'). |
spaceId | string | — | Space/room ID to associate the texture with. Defaults to the current room. |
Parameters from the server's own tool schema.
This tool triggers an external AI image generation service (Google Imagen 4 via Replicate), which constitutes executing an external operation with side effects. It initiates an async job on a third-party platform. While not destructive or financial, it executes compute on external infrastructure and produces artifacts stored externally, placing it firmly in Execute category.
From the tool's definition Generate a seamless PBR texture from a text prompt using Google Imagen 4 Fast (via Replicate). Kicks off an async job
Attacks that exploit this kind of access
Generate a seamless PBR texture from a text prompt using Google Imagen 4 Fast (via Replicate). Kicks off an async job — poll list_generated_textures 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_texture 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_texture: 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_texture 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_texture 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_texture. 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_texture 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 →