Delete a local saved search view.
AI agents call delete_search_view to permanently remove resources in Todos — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes a saved search view configuration that cannot be recovered without external backup. While the blast radius is limited to search view metadata rather than core task data, deletion operations are classified as Destructive per the taxonomy.
From the tool's definition Tool name is 'delete_search_view' with description 'Delete a local saved search view.' The verb 'delete' combined with 'search view' indicates irreversible removal of user-created data.
Attacks that exploit this kind of access
Delete a local saved search view. It is categorised as a Destructive tool in the Todos MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Todos MCP server in PolicyLayer and add a rule for delete_search_view: 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 Todos. Nothing to install.
delete_search_view 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_search_view 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_search_view. 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_search_view is provided by the Todos MCP server (@hasna/todos). 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 →