fw_unfollow
Remove a library follow or channel subscription. Rate-limited: 30/hour.
This record as markdown: /tools/kh0pper-crow/fw-unfollow.md
What fw_unfollow does on Crow
AI agents call fw_unfollow 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_unfollow is rated Critical
Removing a follow or subscription is an irreversible deletion of a relationship/subscription state. While it can technically be re-followed, the act of 'removing' a subscription is a destructive operation that deletes existing state. The rate limit (30/hour) suggests it's a write-like action, but removal/deletion semantics place it in Destructive.
From the tool's definition Remove a library follow or channel subscription
Attacks that exploit this kind of access
The rule that runs fw_unfollow 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_unfollow, this is the rule to start with:
fw_unfollow 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_unfollow call is checked against it from then on.
Questions about fw_unfollow
Remove a library follow or channel subscription. Rate-limited: 30/hour. 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_unfollow: 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_unfollow 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_unfollow 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_unfollow. 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_unfollow 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