Delete the entire local LaunchFrame service cache. Services will be re-downloaded on next use.
AI agents call cli_cache_clear to permanently remove resources in LaunchFrame MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
This tool irreversibly deletes data (the local service cache) without the possibility of reversal. Although the deleted cache can be repopulated by re-downloading, the deletion itself is a destructive action that cannot be directly undone.
From the tool's definition Tool description explicitly states "Delete the entire local LaunchFrame service cache" - the word 'Delete' combined with 'entire' indicates irreversible removal of data.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Delete the entire local LaunchFrame service cache. Services will be re-downloaded on next use. It is categorised as a Destructive tool in the LaunchFrame MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the LaunchFrame MCP server in PolicyLayer and add a rule for cli_cache_clear: 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 LaunchFrame MCP. Nothing to install.
cli_cache_clear 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 cli_cache_clear 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 cli_cache_clear. 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.
cli_cache_clear is provided by the LaunchFrame MCP server (launchframe-dev/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 →