page_screenshot

Capture a page or element screenshot.

SERVERJshookmcp SOURCE@jshookmcp/jshook

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-vmoranv-jshookmcp/page-screenshot.md

WHAT IT DOES

What page_screenshot does on Jshookmcp

AI agents call page_screenshot to retrieve information from Jshookmcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why page_screenshot is rated Low

Screenshots only read visual state; no data is modified or executed.

From the tool's definition Capture a page or element screenshot

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs page_screenshot safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Jshookmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For page_screenshot, this is the rule to start with:

page_screenshot Allowed

page_screenshot is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "page_screenshot": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Jshookmcp, apply this rule, and every page_screenshot call is checked against it from then on.

FAQ

Questions about page_screenshot

What does the page_screenshot tool do? +

Capture a page or element screenshot. It is categorised as a Read tool in the Jshookmcp MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on page_screenshot? +

Register the Jshook MCP server in PolicyLayer and add a rule for page_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 Jshookmcp. Nothing to install.

What risk level is page_screenshot? +

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

Can I rate-limit page_screenshot? +

Yes. Add a rate_limit block to the page_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 page_screenshot completely? +

Set action: deny in the PolicyLayer policy for page_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 page_screenshot? +

page_screenshot is provided by the Jshook MCP server (@jshookmcp/jshook). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Jshook, and thousands of servers like it.

This server

All 736 Jshook tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →