Fetch a random image from picsum.photos with specified dimensions and return as base64-encoded image
AI agents call getRandomImage to retrieve information from Weather 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 publicly available image data from an external service (picsum.photos) and returns it in encoded format. It is a pure read operation with no capability to modify, delete, or execute code. The only parameter is image dimensions, which cannot cause harm. Severity is low because fetching images poses minimal security risk even if misused by an AI agent.
From the tool's definition Tool description states 'Fetch a random image' - retrieval operation with no side effects. Returns base64-encoded image data without modifying any state.
Attacks that exploit this kind of access
Fetch a random image from picsum.photos with specified dimensions and return as base64-encoded image. It is categorised as a Read tool in the Weather MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Weather MCP Server MCP server in PolicyLayer and add a rule for getRandomImage: 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 Weather MCP Server. Nothing to install.
getRandomImage 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 getRandomImage 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 getRandomImage. 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.
getRandomImage is provided by the Weather MCP Server MCP server (mkowalskizoovu/mcp-test). 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 →