AI agents call screenshot to retrieve information from Shotter without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Screenshot capture is a non-destructive observation operation. While it creates a file, this is a benign output artifact. It does not modify simulator state, execute code, delete data, or commit financial transactions. The tool is read-only with respect to the iOS Simulator environment. Severity is low as misuse poses minimal risk—excessive screenshots would only consume disk space, not compromise the system or data.
From the tool's definition Tool performs screenshot capture and save to file with no side effects beyond creating an image file. Description states 'Save a high-quality screenshot' which is a read/capture operation, not a destructive or state-modifying action on the simulator itself.
Attacks that exploit this kind of access
Save a high-quality screenshot to a file. Use this when you need to save a screenshot for the user. It is categorised as a Read tool in the Shotter MCP Server, which means it retrieves data without modifying state.
Register the Shotter MCP server in PolicyLayer and add a rule for screenshot: 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 Shotter. Nothing to install.
screenshot 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 screenshot 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 screenshot. 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.
screenshot is provided by the Shotter MCP server (nathanstitt/shotter). 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 →