Get session statistics: request counts, active tabs, uptime, performance metrics.
AI agents call get_stats 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.
This tool only reads and returns statistical information about an active browser session. It performs no modifications, executions, deletions, or financial operations. The worst-case misuse would be information disclosure about session activity, which is low severity. The context that this is part of an anti-detection browser automation server does not change the risk profile of a read-only statistics tool.
From the tool's definition Tool name 'get_stats' with description stating it retrieves 'session statistics: request counts, active tabs, uptime, performance metrics' — purely informational queries with no side effects.
Documented attack patterns abuse exactly the kind of access get_stats 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 get_stats:
{
"version": "1",
"default": "deny",
"tools": {
"get_stats": {}
}
}get_stats 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 session statistics: request counts, active tabs, uptime, performance metrics. It is categorised as a Read tool in the Camofox MCP Server, which means it retrieves data without modifying state.
Register the Camofox MCP server in PolicyLayer and add a rule for get_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 Camofox. Nothing to install.
get_stats 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_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.
Set action: deny in the PolicyLayer policy for get_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.
get_stats 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.
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.