Save current session as named auth state (e.g. logged-in user). Convenience wrapper: storage_state_save to ~/.camoufox-mcp/sessions/<name>.json
AI agents use auth_capture to create or update resources in MCP Camoufox — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Camoufox environment.
This tool writes authentication state to disk in a structured, named format. While reversible (making it Write rather than Destructive), it has high severity because: (1) it captures and stores authentication credentials in an unencrypted JSON file, (2) an AI agent misusing this could create backdoor access points by storing credentials under attacker-controlled names, (3) the persistence mechanism enables session…
From the tool's definition Tool explicitly performs a 'Save current session' operation, creating a persistent named auth state file at '~/.camoufox-mcp/sessions/<name>.json'.
Documented attack patterns abuse exactly the kind of access auth_capture 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 auth_capture:
{
"version": "1",
"default": "deny",
"tools": {
"auth_capture": {
"limits": [
{
"counter": "auth_capture_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}auth_capture stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Save current session as named auth state (e.g. logged-in user). Convenience wrapper: storage_state_save to ~/.camoufox-mcp/sessions/<name>.json. It is categorised as a Write tool in the MCP Camoufox MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the MCP Camoufox MCP server in PolicyLayer and add a rule for auth_capture: 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.
auth_capture is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the auth_capture 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 auth_capture. 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.
auth_capture 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.