pt_defederate

Full defederation: block + unfollow + purge cached videos from a remote instance. QUEUED — requires operator confirmation.

SERVERCrow SOURCEkh0pper/crow
Critical RISK CLASS
Category Destructive
Parameters 00 required
Recommended Hiddensee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/kh0pper-crow/pt-defederate.md

What pt_defederate does on Crow

AI agents call pt_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 pt_defederate is rated Critical

Purging cached videos and defederating an instance are irreversible actions that permanently remove data and break established connections. Although the tool is queued and requires operator confirmation (mitigating factor), the core operation is destructive. This is more severe than Write (which is reversible) because purged data cannot be recovered automatically.

From the tool's definition 'block + unfollow + purge cached videos from a remote instance' — the tool irreversibly purges cached data and severs federation relationships, effects that cannot be undone without manual intervention.

Questions about pt_defederate

What does the pt_defederate tool do? +

Full defederation: block + unfollow + purge cached videos from a remote instance. 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.

How do I enforce a policy on pt_defederate? +

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

What risk level is pt_defederate? +

pt_defederate 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 pt_defederate? +

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

How do I block pt_defederate completely? +

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

What MCP server provides pt_defederate? +

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

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Crow's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.