저장된 검색을 삭제한다.
AI agents call delete_saved_search to permanently remove resources in Assetcache — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool permanently removes saved search records without possibility of recovery. While the blast radius is moderate (affects only metadata, not core assets), the irreversible nature of deletion places it in the Destructive category rather than Write. Severity is medium rather than high because the impact is scoped to search metadata rather than the asset library itself.
From the tool's definition Tool name 'delete_saved_search' combined with description '저장된 검색을 삭제한다' (Korean: 'Delete the saved search'). The verb 'delete' explicitly indicates irreversible removal of data.
Attacks that exploit this kind of access
저장된 검색을 삭제한다. It is categorised as a Destructive tool in the Assetcache MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Assetcache MCP server in PolicyLayer and add a rule for delete_saved_search: 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 Assetcache. Nothing to install.
delete_saved_search 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_saved_search 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_saved_search. 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_saved_search is provided by the Assetcache MCP server (v0o0v/assetcache-mcp). 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 →