pf_defederate
Defederate from a remote domain (block + purge cached content + sever follows). QUEUED — requires operator confirmation.
This record as markdown: /tools/kh0pper-crow/pf-defederate.md
What pf_defederate does on Crow
AI agents call pf_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 pf_defederate is rated Critical
This tool performs multiple irreversible operations: (1) purging cached content (data deletion), (2) severing follow relationships, and (3) blocking a domain. These actions cannot be undone without manual intervention and represent permanent loss of data/relationships. While marked QUEUED with operator confirmation, the underlying capability is destructive.
From the tool's definition Defederate from a remote domain (block + purge cached content + sever follows). The tool purges cached content and severs follows — both irreversible actions. The word 'purge' indicates deletion of data without recovery option.
Attacks that exploit this kind of access
The rule that runs pf_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 pf_defederate, this is the rule to start with:
pf_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 pf_defederate call is checked against it from then on.
Questions about pf_defederate
Defederate from a remote domain (block + purge cached content + sever follows). QUEUED — requires operator confirmation. 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 pf_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.
pf_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 pf_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 pf_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.
pf_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