cache_stats

Returns cached sessions in memory

Server F1 luffy610/f1-mcp
Category Read
Risk class Low
Parameters 00 required

What cache_stats does on F1

AI agents call cache_stats to retrieve information from F1 without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why cache_stats needs a policy

This tool queries the state of an in-memory cache and returns information about cached Formula 1 session data. It performs a read-only operation without creating, modifying, deleting, or executing any code. The blast radius is minimal—an AI agent cannot cause harm by invoking this tool, as it only retrieves metadata about cached data.

From the tool's definition Tool name 'cache_stats' and description 'Returns cached sessions in memory' indicate a retrieval operation with no modification or side effects.

Questions about cache_stats

What does the cache_stats tool do? +

Returns cached sessions in memory. It is categorised as a Read tool in the F1 MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on cache_stats? +

Register the F1 MCP server in PolicyLayer and add a rule for cache_stats: 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 cache_stats? +

cache_stats is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit cache_stats? +

Yes. Add a rate_limit block to the cache_stats 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 cache_stats completely? +

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

cache_stats 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.