Delete the persistent profile (~/.camoufox-mcp/profile) entirely.
AI agents call reset_profile to permanently remove resources in MCP Camoufox — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently deletes a persistent profile directory without reversibility. The action cannot be undone and represents loss of stored state/configuration. While the blast radius is somewhat constrained (local profile, not global system data), the irreversible nature and complete removal justify the 'Destructive' category over 'Write'.
From the tool's definition Tool description states 'Delete the persistent profile (~/.camoufox-mcp/profile) entirely.' The verb 'delete' combined with 'entirely' indicates irreversible removal of data.
Documented attack patterns abuse exactly the kind of access reset_profile 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 reset_profile:
{
"version": "1",
"default": "deny",
"hide": [
"reset_profile"
]
} reset_profile disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Delete the persistent profile (~/.camoufox-mcp/profile) entirely. It is categorised as a Destructive tool in the MCP Camoufox MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MCP Camoufox MCP server in PolicyLayer and add a rule for reset_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 MCP Camoufox. Nothing to install.
reset_profile is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the reset_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 reset_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.
reset_profile 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.