Take a screenshot of the current page or viewport
AI agents call take_screenshot to retrieve information from Pydoll without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Taking a screenshot captures visual data from the browser without altering the page, executing code, or affecting system state. This is a passive observation operation analogous to viewing a page, making it a Read category tool with low severity. The confidence is high because the description is explicit and unambiguous.
From the tool's definition Tool description states 'Take a screenshot of the current page or viewport' — a retrieval operation with no modifications, side effects, or external state changes.
Documented attack patterns abuse exactly the kind of access take_screenshot gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Pydoll, and nothing reaches the server without passing your rules. This is the rule we recommend for take_screenshot:
{
"version": "1",
"default": "deny",
"tools": {
"take_screenshot": {}
}
}take_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.
Take a screenshot of the current page or viewport. It is categorised as a Read tool in the Pydoll MCP Server, which means it retrieves data without modifying state.
Register the Pydoll MCP server in PolicyLayer and add a rule for 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 Pydoll. Nothing to install.
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 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 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.
take_screenshot is provided by the Pydoll MCP server (jinsongroh/pydoll-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Pydoll, 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.
57 Pydoll tools catalogued and risk-classified — across an index of 43,000+ MCP servers.