Save browser cookies from an active tab to a named profile on disk. Enables session persistence across restarts. Use after login to save authenticated state.
AI agents use save_profile to create or update resources in Camofox — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Camofox environment.
This tool writes data (cookies) to persistent storage, making it a Write operation. Severity is medium because saved cookies could enable unauthorized session hijacking or persistence of compromised authentication states if an agent maliciously saves attacker-controlled credentials, but the tool itself doesn't directly execute commands or cause immediate financial harm.
From the tool's definition The tool saves browser cookies to disk in a named profile, which creates and modifies persistent data files.
Documented attack patterns abuse exactly the kind of access save_profile 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 save_profile:
{
"version": "1",
"default": "deny",
"tools": {
"save_profile": {
"limits": [
{
"counter": "save_profile_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}save_profile 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 browser cookies from an active tab to a named profile on disk. Enables session persistence across restarts. Use after login to save authenticated state. It is categorised as a Write tool in the Camofox MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Camofox MCP server in PolicyLayer and add a rule for save_profile: 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.
save_profile 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 save_profile 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 save_profile. 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.
save_profile 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.