Retrieves the screenshot/preview image of a screen as base64-encoded PNG.
AI agents call get_screen_image to retrieve information from Stitch MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a simple data retrieval operation—fetching an existing screen image. There is no creation, modification, deletion, execution of code, financial transaction, or destructive action. The action is read-only and non-reversible effects are absent. Low severity because the worst-case scenario is exposing a screenshot preview that may already be visible to authorized users.
From the tool's definition Tool name is 'get_screen_image' and description states it 'Retrieves the screenshot/preview image of a screen as base64-encoded PNG.' The verb 'Retrieves' is explicitly a read operation with no modification or side effects.
Attacks that exploit this kind of access
Retrieves the screenshot/preview image of a screen as base64-encoded PNG. It is categorised as a Read tool in the Stitch MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Stitch MCP Server MCP server in PolicyLayer and add a rule for get_screen_image: 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 Stitch MCP Server. Nothing to install.
get_screen_image 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_screen_image 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_screen_image. 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_screen_image is provided by the Stitch MCP Server MCP server (oogleyskr/stitch-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 →