【按需调用】清除检索引擎的文本索引缓存。
AI agents call clear_retrieval_cache to permanently remove resources in LuzzyTool — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Clearing an index cache is an irreversible destructive operation: once the cache/index is wiped, the indexed data is gone and must be rebuilt. This cannot be undone directly, placing it in the Destructive category. Severity is medium because only the cache/index is lost (not source files), but rebuilding a large semantic index can be costly and disruptive.
From the tool's definition 清除检索引擎的文本索引缓存 — 'clear' (清除) of the retrieval engine's text index cache
Attacks that exploit this kind of access
【按需调用】清除检索引擎的文本索引缓存。. It is categorised as a Destructive tool in the LuzzyTool MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the LuzzyTool MCP server in PolicyLayer and add a rule for clear_retrieval_cache: 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 LuzzyTool. Nothing to install.
clear_retrieval_cache 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 clear_retrieval_cache 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 clear_retrieval_cache. 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.
clear_retrieval_cache is provided by the LuzzyTool MCP server (luzzymeow/luzzytool). 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 →