Health check — verify server, browser status, active tabs.
AI agents call server_status 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 only queries and returns the current state of the server and browser (status/health metrics), which is a read-only operation. It has minimal blast radius—an AI agent misusing it cannot cause harm beyond potentially learning internal system state. The low severity reflects that status checks are informational only and do not permit actions on data or systems.
From the tool's definition Tool is described as a 'Health check — verify server, browser status, active tabs.' It retrieves status information without modifying, executing operations, or causing 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 MCP Camoufox, 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.
Health check — verify server, browser status, active tabs. 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 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 MCP Camoufox. 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 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.