page_snapshot

THE RISK

Low Risk

Why page_snapshot needs a policy

This tool reads and queries the current page state through the accessibility tree API, returning data about interactive elements with reference labels. It has no side effects, makes no modifications, executes no code, and performs no destructive operations.

From the tool's definition Tool description explicitly states 'Get a compact accessibility tree snapshot' — retrieves page structure data without modification. Name 'page_snapshot' indicates passive observation.

Documented attack patterns abuse exactly the kind of access page_snapshot gives an agent:

POLICY

How to control page_snapshot

PolicyLayer is an MCP gateway — it sits between your AI agents and Webclaw, and nothing reaches the server without passing your rules. This is the rule we recommend for page_snapshot:

policy.json

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

page_snapshot is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Webclaw — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Webclaw tools

Destructive close_tab Close a browser tab Execute drop_files Drop files onto an element (file input or drag-and-drop target) for uploading Execute hover Hover over an element to trigger mouseover events and reveal hidden UI (e.g., dropdown men Execute invoke_webmcp_tool Invoke a WebMCP tool declared by the current page Execute navigate_to Navigate the browser to a URL Execute new_tab Open a new browser tab Execute wait_for_navigation Wait for the current page to finish loading Execute click Click an element identified by its @ref from the latest page snapshot

All 21 Webclaw tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about page_snapshot

What does the page_snapshot tool do? +

Get a compact accessibility tree snapshot of the current page with @ref labels for interactive elements. It is categorised as a Read tool in the Webclaw MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on page_snapshot? +

Register the Webclaw MCP server in PolicyLayer and add a rule for page_snapshot: 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 Webclaw. Nothing to install.

What risk level is page_snapshot? +

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

Can I rate-limit page_snapshot? +

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

Set action: deny in the PolicyLayer policy for page_snapshot. 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_snapshot? +

page_snapshot is provided by the Webclaw MCP server (kuroko1t/webclaw). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Webclaw tool call.

Start from Webclaw, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →