List all saved browser profiles with metadata. Shows profile names, cookie counts, save dates, and descriptions.
AI agents call list_profiles 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 and queries existing profile information without creating, modifying, executing, or deleting anything. It is purely informational and has no side effects. While the parent server performs browser automation that could be misused, this particular tool is confined to data retrieval operations with minimal security risk.
From the tool's definition Tool description explicitly states it 'List[s] all saved browser profiles with metadata' and 'Shows profile names, cookie counts, save dates, and descriptions.' The verb 'list' combined with read-only metadata retrieval indicates no data modification or…
Documented attack patterns abuse exactly the kind of access list_profiles 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 list_profiles:
{
"version": "1",
"default": "deny",
"tools": {
"list_profiles": {}
}
}list_profiles 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.
List all saved browser profiles with metadata. Shows profile names, cookie counts, save dates, and descriptions. 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 list_profiles: 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.
list_profiles 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 list_profiles 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 list_profiles. 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.
list_profiles 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.