delete_search_view

Delete a local saved search view.

SERVERTodos SOURCE@hasna/todos

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/todos/delete-search-view.md

WHAT IT DOES

What delete_search_view does on Todos

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.

RISK

Why delete_search_view is rated Critical

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

RECOMMENDED RULE

The rule that runs delete_search_view safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Todos, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For delete_search_view, this is the rule to start with:

delete_search_view Hidden

delete_search_view is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "delete_search_view"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Todos, apply this rule, and every delete_search_view call is checked against it from then on.

FAQ

Questions about delete_search_view

What does the delete_search_view tool do? +

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.

How do I enforce a policy on delete_search_view? +

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.

What risk level is delete_search_view? +

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.

Can I rate-limit delete_search_view? +

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.

How do I block delete_search_view completely? +

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.

What MCP server provides delete_search_view? +

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.

KEEP EXPLORING

More on Todos, and thousands of servers like it.

This server

All 528 Todos tools → Critical-risk tools on this server →

Across the catalogue

sms_delete_message on Twilio SMS MCP Server →delete_snapshot on Why Did You Render →calendar_delete_event on Templonix Lite MCP Server →delete_addon_domain on cPanel MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →