page_stats

THE RISK

Low Risk

Why page_stats needs a policy

This tool retrieves statistical information about the current page (element count, size, load metrics) without modifying any state. It is purely a read/query operation used to inform decisions about data extraction strategy.

From the tool's definition Page statistics: element count, size, load metrics. Use to decide extraction strategy.

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

POLICY

How to control page_stats

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 page_stats:

policy.json

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

page_stats 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 MCP Camoufox — 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 MCP Camoufox tools

Destructive cookie_delete Delete cookies. Both empty = clear all. Destructive localstorage_clear Clear all localStorage. Destructive reset_profile Delete the persistent profile (~/.camoufox-mcp/profile) entirely. Destructive browser_close Close the browser. Cookies are preserved in the persistent profile (~/.camoufox-mcp/profil Destructive tab_close Close a tab by index (-1 = active), or by url_contains. Execute batch_actions Execute multiple actions in one call. Each action: {type, ref?, value?, text?, key?, url?} Execute browser_launch Launch Camoufox stealth browser and navigate to URL. Browser persists between calls. Execute evaluate Execute JavaScript in page context.

All 102 MCP Camoufox 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_stats

What does the page_stats tool do? +

Page statistics: element count, size, load metrics. Use to decide extraction strategy. 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 page_stats? +

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

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

Can I rate-limit page_stats? +

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

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

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

CHECK YOUR STACK →