gts_defederate

Defederate from a remote domain (stop all ActivityPub interaction). Stronger than block_domain — existing follow relationships are severed. 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/gts-defederate.md

What gts_defederate does on Crow

AI agents call gts_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 gts_defederate is rated Critical

This tool irreversibly severs all existing follow relationships with a remote domain and halts all ActivityPub interaction. Severing follow relationships is a destructive action that cannot be automatically undone — affected users lose their connections. The description explicitly notes it is 'stronger than block_domain,' indicating a higher severity of impact.

From the tool's definition Defederate from a remote domain (stop all ActivityPub interaction). Stronger than block_domain — existing follow relationships are severed.

Questions about gts_defederate

What does the gts_defederate tool do? +

Defederate from a remote domain (stop all ActivityPub interaction). Stronger than block_domain — existing follow relationships are severed. 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 gts_defederate? +

Register the Crow MCP server in PolicyLayer and add a rule for gts_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 gts_defederate? +

gts_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 gts_defederate? +

Yes. Add a rate_limit block to the gts_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 gts_defederate completely? +

Set action: deny in the PolicyLayer policy for gts_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 gts_defederate? +

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