Deletes a saved search by name
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.
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.
Attacks that exploit this kind of access
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.
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.
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.
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.
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.
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.
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 →