cache_stats · OpenAPI Directory MCP Server MCP

WHAT IT DOES

What cache_stats does on OpenAPI Directory MCP Server

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

THE RISK

Low Risk

Why cache_stats needs a policy

This tool retrieves and reports cache statistics and performance metrics—purely informational operations with no side effects, data modification, code execution, or resource consumption beyond reading metrics. It aligns with the 'Read' category as it queries existing state without any reversible or irreversible changes.

From the tool's definition Tool name 'cache_stats' and description 'Get cache statistics and performance metrics' indicate a query operation that retrieves diagnostic information without modifying or executing any operations.

Documented attack patterns abuse exactly the kind of access cache_stats gives an agent:

POLICY

How to control cache_stats

PolicyLayer is an MCP gateway — it sits between your AI agents and OpenAPI Directory MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for cache_stats:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "cache_stats": {}
  }
}

cache_stats is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register OpenAPI Directory MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More OpenAPI Directory MCP Server tools

Destructive clear_cache Clear all cache entries Destructive clear_cache_key Clear a specific cache key Read analyze_api_categories Analyze API distribution by categories Read cache_info Get cache configuration and settings Read get_api Get detailed information about a specific API Read get_api_summary Get basic information about a specific API without endpoint details Read get_endpoint_details Get detailed information about a specific API endpoint Read get_endpoint_examples Get request and response examples for a specific API endpoint

All 22 OpenAPI Directory MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about cache_stats

What does the cache_stats tool do? +

Get cache statistics and performance metrics. It is categorised as a Read tool in the OpenAPI Directory MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on cache_stats? +

Register the OpenAPI Directory MCP Server 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 OpenAPI Directory MCP Server. 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 OpenAPI Directory MCP Server MCP server (rawveg/openapi-directory-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every OpenAPI Directory MCP Server tool call.

Start from OpenAPI Directory MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →

Free to start. No card required.

22 OpenAPI Directory MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.