get-cache-stats

THE RISK

Low Risk

Why get-cache-stats needs a policy

This tool retrieves and reports cache statistics—purely observational data about system performance. There are no side effects, no data modification, no code execution, and no destructive operations. It falls squarely into the Read category with low severity since misuse would only expose non-sensitive operational metrics.

From the tool's definition Tool name 'get-cache-stats' and description 'Read cache statistics for files/metadata/search/templates' explicitly indicate a read-only operation that retrieves statistical information without modifying, deleting, or executing any operations.

Documented attack patterns abuse exactly the kind of access get-cache-stats gives an agent:

POLICY

How to control get-cache-stats

PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Prompt Manager, and nothing reaches the server without passing your rules. This is the rule we recommend for get-cache-stats:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "get-cache-stats": {}
  }
}

get-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 MCP Prompt Manager — 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 MCP Prompt Manager tools

Destructive delete-prompt Delete a prompt file Execute process-template Process a prompt template with advanced logic Write favorite-prompt Add or remove a prompt from favorites Write rollback-prompt Rollback a prompt to a specific version Write categorize-prompt Set category for a prompt Write create-prompt Create a new prompt file Write create-prompt-from-template Create a new prompt file from a template with variables Write export-prompts Export prompts to JSON format for backup or sharing

All 33 MCP Prompt Manager 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 get-cache-stats

What does the get-cache-stats tool do? +

Read cache statistics for files/metadata/search/templates. It is categorised as a Read tool in the MCP Prompt Manager MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get-cache-stats? +

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

What risk level is get-cache-stats? +

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

Can I rate-limit get-cache-stats? +

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

Set action: deny in the PolicyLayer policy for get-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 get-cache-stats? +

get-cache-stats is provided by the MCP Prompt Manager MCP server (tae4an/mcp-prompt-manager). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every MCP Prompt Manager tool call.

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

CHECK YOUR STACK →