clear_cache

Clears session cache

Server F1 luffy610/f1-mcp
Category Destructive
Risk class Critical
Parameters 00 required

What clear_cache does on F1

AI agents call clear_cache to permanently remove resources in F1 — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why clear_cache needs a policy

Clearing a cache permanently removes stored session data. While the underlying data may still be retrievable from its source, the cached copies are irreversibly deleted, requiring re-computation or re-fetching. This fits the Destructive category. Severity is medium as it affects performance/availability but not primary data sources.

From the tool's definition 'Clears session cache' — clearing cache is an irreversible deletion of cached data

Questions about clear_cache

What does the clear_cache tool do? +

Clears session cache. It is categorised as a Destructive tool in the F1 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 clear_cache? +

Register the F1 MCP server in PolicyLayer and add a rule for clear_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 F1. Nothing to install.

What risk level is clear_cache? +

clear_cache 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 clear_cache? +

Yes. Add a rate_limit block to the clear_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.

How do I block clear_cache completely? +

Set action: deny in the PolicyLayer policy for clear_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.

What MCP server provides clear_cache? +

clear_cache is provided by the F1 MCP server (luffy610/f1-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.