AI agents call take_screenshot_with_ocr to retrieve information from Computer Control MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool captures visual information from the screen and performs OCR (optical character recognition) to extract text. Both screenshot capture and OCR are read-only operations with no side effects—they retrieve data without modifying system state, user data, or triggering external actions. The minimal blast radius (information disclosure only if misused) supports a 'low' severity rating.
From the tool's definition Tool name 'take_screenshot_with_ocr' indicates reading/capturing screen content and extracting text via OCR. The server description confirms this is part of 'screenshot capture' functionality.
Documented attack patterns abuse exactly the kind of access take_screenshot_with_ocr gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Computer Control MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for take_screenshot_with_ocr:
{
"version": "1",
"default": "deny",
"tools": {
"take_screenshot_with_ocr": {}
}
}take_screenshot_with_ocr is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
take_screenshot_with_ocr. It is categorised as a Read tool in the Computer Control MCP MCP Server, which means it retrieves data without modifying state.
Register the Computer Control MCP server in PolicyLayer and add a rule for take_screenshot_with_ocr: 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 Computer Control MCP. Nothing to install.
take_screenshot_with_ocr 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 take_screenshot_with_ocr 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 take_screenshot_with_ocr. 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.
take_screenshot_with_ocr is provided by the Computer Control MCP server (ab498/computer-control-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 15 Computer Control MCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
15 Computer Control MCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.