AI agents call capture_screenshot to retrieve information from PC-MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool captures a screenshot and saves it to a file. It reads the current screen state (Read), but saving to a file is a minor Write side effect. However, the primary concern is privacy — it can capture sensitive on-screen information visible to the agent. The most accurate category is Read since it retrieves visual data from the screen.
From the tool's definition 截取屏幕并保存为文件 (Capture screen and save as file)
Documented attack patterns abuse exactly the kind of access capture_screenshot gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and PC-MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for capture_screenshot:
{
"version": "1",
"default": "deny",
"tools": {
"capture_screenshot": {}
}
}capture_screenshot 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.
截取屏幕并保存为文件. It is categorised as a Read tool in the PC-MCP MCP Server, which means it retrieves data without modifying state.
Register the PC- MCP server in PolicyLayer and add a rule for capture_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-MCP. Nothing to install.
capture_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_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_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_screenshot is provided by the PC- MCP server (shijianzhong/mcp-server-for-pc). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from PC-MCP, 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.
6 PC-MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.