New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

delete-log-viewer-saved-search-by-name

Deletes a saved search by name

SERVERMcp Dev SOURCE@umbraco-cms/mcp-dev
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/mcp-dev/delete-log-viewer-saved-search-by-name.md

What delete-log-viewer-saved-search-by-name does on Mcp Dev

AI agents call delete-log-viewer-saved-search-by-name to permanently remove resources in Mcp Dev, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why delete-log-viewer-saved-search-by-name is rated Critical

The tool performs an irreversible deletion of a saved search artifact. While the data being deleted (a saved search configuration) is not critical business data like documents or media, the action is permanent and non-reversible, fitting the Destructive category.

From the tool's definition Tool name contains 'delete' and description states 'Deletes a saved search by name' - this is an irreversible deletion operation that cannot be undone.

Questions about delete-log-viewer-saved-search-by-name

What does the delete-log-viewer-saved-search-by-name tool do? +

Deletes a saved search by name. It is categorised as a Destructive tool in the Mcp Dev 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-log-viewer-saved-search-by-name? +

Register the Mcp Dev MCP server in PolicyLayer and add a rule for delete-log-viewer-saved-search-by-name: 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 Dev. Nothing to install.

What risk level is delete-log-viewer-saved-search-by-name? +

delete-log-viewer-saved-search-by-name 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-log-viewer-saved-search-by-name? +

Yes. Add a rate_limit block to the delete-log-viewer-saved-search-by-name 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-log-viewer-saved-search-by-name completely? +

Set action: deny in the PolicyLayer policy for delete-log-viewer-saved-search-by-name. 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-log-viewer-saved-search-by-name? +

delete-log-viewer-saved-search-by-name is provided by the Mcp Dev MCP server (@umbraco-cms/mcp-dev). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Mcp Dev, 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 Mcp Dev'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.