take_screenshot

Take a screenshot of the currently selected page. By default captures the visible viewport; set fullPage=true to capture the full page.

Server JS Reverse MCP zhizhuodemao/js-reverse-mcp
Category Read
Risk class Low
Parameters 00 required

What take_screenshot does on JS Reverse MCP

AI agents call take_screenshot to retrieve information from JS Reverse MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why take_screenshot needs a policy

Screenshot capture is a passive information retrieval operation that observes the current state of a web page without modifying data, executing code, or causing side effects. The blast radius of misuse is minimal—it could expose visual information about a user's page, but cannot alter state or trigger actions. This is clearly a Read operation.

From the tool's definition Tool description states 'Take a screenshot of the currently selected page' with options to capture 'visible viewport' or 'full page'. No modification, deletion, code execution, or financial operations are involved.

Questions about take_screenshot

What does the take_screenshot tool do? +

Take a screenshot of the currently selected page. By default captures the visible viewport; set fullPage=true to capture the full page. It is categorised as a Read tool in the JS Reverse MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on take_screenshot? +

Register the JS Reverse 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 JS Reverse MCP. Nothing to install.

What risk level is take_screenshot? +

take_screenshot is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit take_screenshot? +

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.

How do I block take_screenshot completely? +

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.

What MCP server provides take_screenshot? +

take_screenshot is provided by the JS Reverse MCP server (zhizhuodemao/js-reverse-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.