Low Risk

browser_snapshot

Get visible interactive elements with ref IDs. Use refs with click/fill. Always call after navigation.

How to control browser_snapshot ↓

What browser_snapshot does on MCP Camoufox

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

Low Risk

Why browser_snapshot needs a policy

This tool queries the current state of the browser DOM to identify interactive elements and assign reference IDs for use by other tools. It performs data retrieval only, with no capacity to modify, execute, or delete anything. While the server as a whole is designed for 'undetectable web automation' and 'bypassing bot detection,' this specific tool is a non-destructive read operation.

From the tool's definition Tool description states it 'Get[s] visible interactive elements with ref IDs' - a retrieval operation with no side effects. The phrase 'Always call after navigation' indicates it captures state rather than modifying it.

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

How to control browser_snapshot

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

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "browser_snapshot": {}
  }
}

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

  1. Create a free account and register MCP Camoufox — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about browser_snapshot

What does the browser_snapshot tool do? +

Get visible interactive elements with ref IDs. Use refs with click/fill. Always call after navigation. It is categorised as a Read tool in the MCP Camoufox MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on browser_snapshot? +

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

What risk level is browser_snapshot? +

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

Can I rate-limit browser_snapshot? +

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

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

browser_snapshot is provided by the MCP Camoufox MCP server (robithyusuf/mcp-camoufox). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MCP Camoufox tool call.

Start from MCP Camoufox, 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.

102 MCP Camoufox tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.