Capture a full-page screenshot (returns base64).
AI agents call screenshot_page to retrieve information from OODA Computer Control without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool purely captures and returns screen state without altering system or data. It is a read-only operation. While screenshots could theoretically expose sensitive information on-screen, the tool itself has no destructive, executable, or write capabilities. Severity is low because the impact depends entirely on what happens to be visible on the screen at capture time, not on the tool's inherent capabilities.
From the tool's definition Tool name and description: 'Capture a full-page screenshot (returns base64)' — retrieves visual data from the screen with no side effects, no modification, no execution, no deletion.
Documented attack patterns abuse exactly the kind of access screenshot_page gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and OODA Computer Control, and nothing reaches the server without passing your rules. This is the rule we recommend for screenshot_page:
{
"version": "1",
"default": "deny",
"tools": {
"screenshot_page": {}
}
}screenshot_page 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.
Capture a full-page screenshot (returns base64). It is categorised as a Read tool in the OODA Computer Control MCP Server, which means it retrieves data without modifying state.
Register the OODA Computer Control MCP server in PolicyLayer and add a rule for screenshot_page: 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 OODA Computer Control. Nothing to install.
screenshot_page 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_page 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_page. 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_page is provided by the OODA Computer Control MCP server (mnehmos/mnehmos.ooda.mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from OODA Computer Control, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
99 OODA Computer Control tools catalogued and risk-classified — across an index of 43,000+ MCP servers.