Permanently delete a saved article from Wallabag
AI agents call crow_wallabag_delete 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.
This tool performs an irreversible deletion operation on user data (saved articles). Once executed, the article cannot be recovered. This meets the Destructive category definition: 'irreversibly deletes or overwrites data, or actions that cannot be undone.' Severity is high because an AI agent with misconfigured instructions could permanently lose user-saved content, causing data loss.
From the tool's definition Tool name includes 'delete' and description states 'Permanently delete a saved article from Wallabag' — irreversible removal of data.
Documented attack patterns abuse exactly the kind of access crow_wallabag_delete gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Crow, and nothing reaches the server without passing your rules. This is the rule we recommend for crow_wallabag_delete:
{
"version": "1",
"default": "deny",
"hide": [
"crow_wallabag_delete"
]
} crow_wallabag_delete disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Permanently delete a saved article from Wallabag. 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 crow_wallabag_delete: 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.
crow_wallabag_delete 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 crow_wallabag_delete 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 crow_wallabag_delete. 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.
crow_wallabag_delete 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.
Start from Crow, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
576 Crow tools catalogued and risk-classified — across an index of 43,000+ MCP servers.