crow_miniflux_remove_feed

Unsubscribe from a feed. This removes the feed and all its entries permanently.

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/crow-miniflux-remove-feed.md

What crow_miniflux_remove_feed does on Crow

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

This tool permanently deletes feed subscriptions and their associated entries, which cannot be undone. This meets the Destructive category definition: 'irreversibly deletes or overwrites data, or actions that cannot be undone.' The high severity reflects that an AI agent misusing this could permanently remove many feeds and historical data. Confidence is high because the destructive nature is explicitly stated.

From the tool's definition 'removes the feed and all its entries permanently' — the description explicitly indicates irreversible deletion of data without recovery option.

Questions about crow_miniflux_remove_feed

What does the crow_miniflux_remove_feed tool do? +

Unsubscribe from a feed. This removes the feed and all its entries permanently. 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 crow_miniflux_remove_feed? +

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

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

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

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

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