AI agents call get_page_errors 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 passively reads and reports JavaScript console errors that have already occurred on a page. It does not modify, delete, or execute code—it merely retrieves diagnostic information. While the broader server context involves stealth automation and bot detection evasion (which raises ethical concerns), this specific tool's function is purely observational.
From the tool's definition The tool 'get_page_errors' retrieves JavaScript errors from the page. The verb 'get' and the read-only nature of querying error logs indicate data retrieval with no side effects.
Documented attack patterns abuse exactly the kind of access get_page_errors 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 get_page_errors:
{
"version": "1",
"default": "deny",
"tools": {
"get_page_errors": {}
}
}get_page_errors 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.
Get JavaScript errors from the page. 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 get_page_errors: 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.
get_page_errors 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 get_page_errors 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 get_page_errors. 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.
get_page_errors 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.