Generate a dynamic delivery URL for an asset with transformation parameters (e.g. width, height, format, smart crop)
AI agents call get_rendered_asset_url to retrieve information from Picsha AI MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and formats asset data for consumption without creating, modifying, or deleting underlying assets. It is a read operation: it fetches or constructs a delivery URL with optional display transformations.
From the tool's definition Tool description states it 'Generate[s] a dynamic delivery URL for an asset with transformation parameters' — a retrieval operation that returns a URL. The verb 'generate' refers to constructing a delivery URL, not modifying or deleting the asset itself.
Attacks that exploit this kind of access
Generate a dynamic delivery URL for an asset with transformation parameters (e.g. width, height, format, smart crop). It is categorised as a Read tool in the Picsha AI MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Picsha AI MCP Server MCP server in PolicyLayer and add a rule for get_rendered_asset_url: 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 Picsha AI MCP Server. Nothing to install.
get_rendered_asset_url 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 get_rendered_asset_url 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 get_rendered_asset_url. 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.
get_rendered_asset_url is provided by the Picsha AI MCP Server MCP server (picsha-ai/mcp-server). 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 →