fw_defederate
Full defederation: block domain + purge cached content. QUEUED — requires operator confirmation in the Nest panel.
This record as markdown: /tools/kh0pper-crow/fw-defederate.md
What fw_defederate does on Crow
AI agents call fw_defederate to permanently remove resources in Crow, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why fw_defederate is rated Critical
This tool performs two irreversible operations: blocking a domain and purging cached content. Purging is explicitly destructive (data deletion), and full defederation prevents future interactions. While it requires operator confirmation (mitigating factor), the underlying capability to permanently remove cached data and block domains qualifies as Destructive rather than Write.
From the tool's definition "Full defederation: block domain + purge cached content" — the tool irreversibly purges cached content and blocks a domain, both of which cannot be undone without manual intervention and represent permanent data loss.
Attacks that exploit this kind of access
The rule that runs fw_defederate safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Crow, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For fw_defederate, this is the rule to start with:
fw_defederate is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Crow, apply this rule, and every fw_defederate call is checked against it from then on.
Questions about fw_defederate
Full defederation: block domain + purge cached content. QUEUED — requires operator confirmation in the Nest panel. It is categorised as a Destructive tool in the Crow MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Crow MCP server in PolicyLayer and add a rule for fw_defederate: 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 Crow. Nothing to install.
fw_defederate 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 fw_defederate 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 fw_defederate. 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.
fw_defederate is provided by the Crow MCP server (kh0pper/crow). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Crow, and thousands of servers like it.
Across the catalogue