AI agents call list_generated_textures to retrieve information from Portals without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries data about generated textures belonging to the current user. It has no side effects—it only returns information about existing textures. The mention of polling results indicates it monitors status rather than modifying or deleting data. This is a straightforward Read operation with minimal risk if misused.
From the tool's definition Tool name contains 'list' and description explicitly states it 'List[s] all AI-generated textures' and 'Returns each texture with its URL...status, and timestamps'. No modification, deletion, or execution of external operations occurs.
Attacks that exploit this kind of access
List all AI-generated textures for the current user. Returns each texture with its URL (empty while still generating), status, and timestamps. Use this to poll results from generate_ai_texture. It is categorised as a Read tool in the Portals MCP Server, which means it retrieves data without modifying state.
Register the Portals MCP server in PolicyLayer and add a rule for list_generated_textures: 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.
list_generated_textures is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_generated_textures 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 list_generated_textures. 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.
list_generated_textures 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 →