Low Risk

camofox_get_page_html

Get rendered HTML from the live DOM. Use when snapshot refs are incomplete on SPA/custom-component sites or when you need the final DOM state rather than the accessibility tree. Optionally pass a CSS selector to return only that element

How to control camofox_get_page_html ↓

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

Low Risk

The tool reads and returns DOM state ('get rendered HTML', 'return only that element') without side effects. However, severity is medium rather than low because: (1) it's a browser automation tool that can inspect sensitive page content, credentials, or user data rendered in the DOM; (2) the broader server context ('Anti-detection browser automation') suggests potential for unauthorized reconnaissance; (3) an…

From the tool's definition Tool 'camofox_get_page_html' retrieves rendered HTML from DOM with optional CSS selector filtering. No modification, deletion, or execution of external commands—purely data retrieval.

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

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

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

camofox_get_page_html 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 Camofox — 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 camofox_get_page_html tool do? +

Get rendered HTML from the live DOM. Use when snapshot refs are incomplete on SPA/custom-component sites or when you need the final DOM state rather than the accessibility tree. Optionally pass a CSS selector to return only that element. It is categorised as a Read tool in the Camofox MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on camofox_get_page_html? +

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

What risk level is camofox_get_page_html? +

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

Can I rate-limit camofox_get_page_html? +

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

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

camofox_get_page_html is provided by the Camofox MCP server (redf0x1/camofox-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Camofox tool call.

Deterministic rules across all 47 Camofox tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

47 Camofox 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.