Captures a screenshot of the currently booted iOS simulator. Returns the image as base64-encoded data.
AI agents call capture_simulator_screenshot to retrieve information from MCP Connect without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves visual state information from a simulator without modifying, executing code, deleting data, or affecting system state. While screenshots could theoretically reveal sensitive information visible on screen, the tool itself is a passive read operation. Severity is low because the risk depends entirely on what content happens to be displayed, not on the tool's inherent capability to cause harm.
From the tool's definition Tool 'capture_simulator_screenshot' performs screenshot capture with no side effects—it only retrieves and returns image data as base64-encoded output.
Attacks that exploit this kind of access
Captures a screenshot of the currently booted iOS simulator. Returns the image as base64-encoded data. It is categorised as a Read tool in the MCP Connect MCP Server, which means it retrieves data without modifying state.
Register the MCP Connect MCP server in PolicyLayer and add a rule for capture_simulator_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 MCP Connect. Nothing to install.
capture_simulator_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 capture_simulator_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 capture_simulator_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.
capture_simulator_screenshot is provided by the MCP Connect MCP server (plaintest/mcp-connect). 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 →