Take a screenshot of the primary monitor.
AI agents call screen_take_screenshot to retrieve information from PC-Control MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves visual information from the display without causing side effects, modifying system state, or executing arbitrary operations. While the server as a whole enables Execute and Destructive actions (via system_execute_command), this specific tool is narrowly scoped to capture and return screenshot data.
From the tool's definition Tool name 'screen_take_screenshot' and description 'Take a screenshot of the primary monitor' indicate data retrieval with no modification, deletion, or execution of commands. Screenshots are read-only captures of visual state.
Attacks that exploit this kind of access
Take a screenshot of the primary monitor. It is categorised as a Read tool in the PC-Control MCP Server MCP Server, which means it retrieves data without modifying state.
Register the PC-Control MCP Server MCP server in PolicyLayer and add a rule for screen_take_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 PC-Control MCP Server. Nothing to install.
screen_take_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 screen_take_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 screen_take_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.
screen_take_screenshot is provided by the PC-Control MCP Server MCP server (krsnmlna1/mcp). 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 →