Delete a category. Feeds in this category become uncategorized.
AI agents call delete_category_tool to permanently remove resources in MCP Feed Reader — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently deletes data (a category) and modifies the state of related feeds. Deletion is irreversible, making it Destructive rather than Write. While the blast radius is limited to feed organization metadata rather than financial or system-level damage, the high confidence reflects the clear destructive nature of the operation.
From the tool's definition Tool name includes 'delete' and description states 'Delete a category.' The action irreversibly removes a category and reorganizes associated feeds to uncategorized status, which cannot be undone.
Attacks that exploit this kind of access
Delete a category. Feeds in this category become uncategorized. It is categorised as a Destructive tool in the MCP Feed Reader MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the MCP Feed Reader MCP server in PolicyLayer and add a rule for delete_category_tool: 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 MCP Feed Reader. Nothing to install.
delete_category_tool 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 delete_category_tool 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 delete_category_tool. 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.
delete_category_tool is provided by the MCP Feed Reader MCP server (pypi:mcp-feed-reader-crunchtools). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →