delete_profile

THE RISK

Critical Risk

This tool permanently deletes stored browser profile data without reversibility. While not financial or life-critical, deletion of user profiles could constitute loss of important browsing state, credentials, or automation configurations. The action cannot be undone, placing it in the Destructive category with high severity due to potential data loss impact in an automated context.

From the tool's definition Tool name is 'delete_profile' and description states 'Delete a saved browser profile from disk. Removes the profile' — explicit use of 'Delete' and 'Removes' indicate irreversible data removal.

Documented attack patterns abuse exactly the kind of access delete_profile gives an agent:

HOW TO CONTROL DELETE_PROFILE

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 delete_profile:

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_profile"
  ]
}

delete_profile disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

Create a free account and register Camofox — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RESTRICT THIS TOOL →

Free to start. No card required.

EXPLORE

More Camofox tools

Destructive delete_download Delete a downloaded file from disk and registry Execute camofox_evaluate_js Execute JavaScript in the browser page context. Runs in isolated scope (invisible to page Execute camofox_hover Hover over an element to trigger tooltips, dropdown menus, or hover states. Use ref from s Execute camofox_wait_for Wait for page to be fully ready (DOM loaded, network idle, framework hydration complete). Execute camofox_wait_for_selector Wait for a CSS selector to appear in the live DOM. Use for SPA hydration and async content Execute camofox_wait_for_text Wait for specific text to appear on the page. Useful for waiting for search results, form Execute navigate Navigate a tab to a URL. Waits for page load. Use create_tab first, then navigate. Returns Execute navigate_and_snapshot Navigate to a URL and return the page snapshot. Combines navigate + wait + snapshot into o

All 47 Camofox tools →

Destructive tools on other servers

Frida Game Hacking MCP clear_scan MegaMemory remove_concept Frida Agent MCP kill_app 1MCP Server mcp_uninstall

Go deeper

Critical-risk tools in Camofox → Every critical-risk tool this server exposes, in one view.
All critical-risk MCP tools → Every critical-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

What does the delete_profile tool do? +

Delete a saved browser profile from disk. Removes the profile. It is categorised as a Destructive tool in the Camofox MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on delete_profile? +

Register the Camofox MCP server in PolicyLayer and add a rule for delete_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.

What risk level is delete_profile? +

delete_profile is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit delete_profile? +

Yes. Add a rate_limit block to the delete_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.

How do I block delete_profile completely? +

Set action: deny in the PolicyLayer policy for delete_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.

What MCP server provides delete_profile? +

delete_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.

Enforce policy on every Camofox tool call.

Deterministic rules across all 47 Camofox tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

GOVERN CAMOFOX →

Free to start. No card required.

47 Camofox tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// WHAT DELETE_PROFILE ON CAMOFOX DOES

// THE RISK

// HOW TO CONTROL DELETE_PROFILE

// EXPLORE