Get a proxy URL for a Sage image that can be accessed by clients.
AI agents call get_image_proxy_url to retrieve information from Sage 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 or generates a proxy URL to access image data—a read operation. It does not create, modify, delete, or execute external operations. The URL itself is a pointer to data, not an action that modifies system state. No financial, destructive, or code-execution implications are evident. Severity is low because accessing an image URL poses minimal risk even if misused by an agent.
From the tool's definition Tool name 'get_image_proxy_url' and description 'Get a proxy URL for a Sage image that can be accessed by clients' indicate retrieval of a URL for accessing existing image data.
Attacks that exploit this kind of access
Get a proxy URL for a Sage image that can be accessed by clients. It is categorised as a Read tool in the Sage MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Sage MCP Server MCP server in PolicyLayer and add a rule for get_image_proxy_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 Sage MCP Server. Nothing to install.
get_image_proxy_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_image_proxy_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_image_proxy_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_image_proxy_url is provided by the Sage MCP Server MCP server (waggle-sensor/sage-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 →