Remove installed hooks and restore original objects in-place. Args: keep_persistent: If True, keep persistent init_scripts registered. Returns: dict with status, restored_objects, cleared counts.
AI agents call remove_hooks to permanently remove resources in Camoufox Reverse — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
An AI agent that decides to call remove_hooks doesn't hesitate, doesn't double-check, and doesn't stop at one. Whatever it removes from Camoufox Reverse is gone — there is no undo for destructive operations.
Documented attack patterns abuse exactly the kind of access remove_hooks gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Camoufox Reverse, and nothing reaches the server without passing your rules. This is the rule we recommend for remove_hooks:
{
"version": "1",
"default": "deny",
"hide": [
"remove_hooks"
]
}remove_hooks 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.
Remove installed hooks and restore original objects in-place. Args: keep_persistent: If True, keep persistent init_scripts registered. Returns: dict with status, restored_objects, cleared counts. It is categorised as a Destructive tool in the Camoufox Reverse MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Camoufox Reverse MCP server in PolicyLayer and add a rule for remove_hooks: 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 Camoufox Reverse. Nothing to install.
remove_hooks 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 remove_hooks 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 remove_hooks. 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.
remove_hooks is provided by the Camoufox Reverse MCP server (whitenightshadow/camoufox-reverse-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 36 Camoufox Reverse tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
36 Camoufox Reverse tools catalogued and risk-classified — across an index of 42,500+ MCP servers.