High Risk →

reload_and_snapshot

Reload page + return snapshot.

How to control reload_and_snapshot ↓

What reload_and_snapshot does on MCP Camoufox

AI agents invoke reload_and_snapshot to trigger actions in MCP Camoufox. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

High Risk

Why reload_and_snapshot needs a policy

This tool triggers a browser action (page reload) which is an external operation that can cause side effects such as re-submitting forms, re-triggering network requests, or resetting page state. The reload is an execution action, and the snapshot is a read component. Per the rules, the most severe applicable category is Execute.

From the tool's definition Reload page + return snapshot

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

How to control reload_and_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 reload_and_snapshot:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "reload_and_snapshot": {
      "limits": [
        {
          "counter": "reload_and_snapshot_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

reload_and_snapshot stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. 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.
RATE-LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about reload_and_snapshot

What does the reload_and_snapshot tool do? +

Reload page + return snapshot. It is categorised as a Execute tool in the MCP Camoufox MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on reload_and_snapshot? +

Register the MCP Camoufox MCP server in PolicyLayer and add a rule for reload_and_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 reload_and_snapshot? +

reload_and_snapshot is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit reload_and_snapshot? +

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

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

reload_and_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.