Compact LLM-friendly page summary (title, heading, key buttons, forms). Cheaper than browser_snapshot for agent context.
AI agents call describe_page 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.
This tool queries and reads page structure/metadata to provide context to the LLM agent. It has no side effects, does not execute code, and does not modify data. The blast radius of misuse is minimal—an agent using this tool can only retrieve page information that is already visible, presenting a low-severity information disclosure risk at most.
From the tool's definition Tool provides a 'page summary' that retrieves and returns page information (title, heading, buttons, forms) without modifying or executing actions. Description explicitly states it summarizes page content.
Documented attack patterns abuse exactly the kind of access describe_page gives an agent:
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 describe_page:
{
"version": "1",
"default": "deny",
"tools": {
"describe_page": {}
}
}describe_page is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Compact LLM-friendly page summary (title, heading, key buttons, forms). Cheaper than browser_snapshot for agent context. It is categorised as a Read tool in the MCP Camoufox MCP Server, which means it retrieves data without modifying state.
Register the MCP Camoufox MCP server in PolicyLayer and add a rule for describe_page: 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.
describe_page is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the describe_page 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.
Set action: deny in the PolicyLayer policy for describe_page. 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.
describe_page 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.
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.