Check CamoFox server health and browser connection. Call first to verify server is running. Returns version, browser status, and active tab count.
AI agents call server_status 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 retrieves system status information without modifying any state, executing code, or performing actions. It is a diagnostic/monitoring function analogous to a health check endpoint. The query nature and lack of side effects place it clearly in the Read category. Severity is low because misuse of a status check alone cannot cause harm—it only returns operational metrics.
From the tool's definition Tool description states it 'Check[s] CamoFox server health and browser connection' and 'Returns version, browser status, and active tab count.' These are purely informational queries with no side effects.
Documented attack patterns abuse exactly the kind of access server_status 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 server_status:
{
"version": "1",
"default": "deny",
"tools": {
"server_status": {}
}
}server_status 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.
Check CamoFox server health and browser connection. Call first to verify server is running. Returns version, browser status, and active tab count. 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 server_status: 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.
server_status 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 server_status 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 server_status. 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.
server_status 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.