Low Risk

get_page_info

Get current page URL, title, and viewport size.

How to control get_page_info ↓

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

Low Risk

This tool only queries static page properties (URL, title, viewport dimensions). It performs a retrieval operation analogous to fetching metadata, with no capacity to modify state, execute code, or trigger external operations. The server's broader anti-detection purpose is noted, but this specific tool is a passive information gather.

From the tool's definition Tool retrieves page metadata: 'Get current page URL, title, and viewport size' — these are read-only queries with no modification or side effects.

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

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

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

get_page_info 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 Camoufox Reverse — 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.

Go deeper

What does the get_page_info tool do? +

Get current page URL, title, and viewport size. It is categorised as a Read tool in the Camoufox Reverse MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_page_info? +

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

What risk level is get_page_info? +

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

Can I rate-limit get_page_info? +

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

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

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

Enforce policy on every Camoufox Reverse tool call.

Deterministic rules across all 36 Camoufox Reverse tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

36 Camoufox Reverse tools catalogued and risk-classified — across an index of 42,500+ 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.