cache_stats

cache_stats

Server Coin sweetcornna/coin-mcp
Category Read
Risk class Low
Parameters 00 required

What cache_stats does on Coin

AI agents call cache_stats to retrieve information from Coin 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

With no description provided, confidence is moderately reduced. However, the name strongly suggests a diagnostic/informational function that queries cache state. No evidence of side effects, data modification, execution, destruction, or financial impact. Classified as Read with low severity since it merely retrieves internal metrics.

From the tool's definition Tool name 'cache_stats' with empty description; based on naming convention in a market-data server context, this appears to retrieve cache statistics/metrics rather than modify data.

Questions about cache_stats

What does the cache_stats tool do? +

cache_stats. It is categorised as a Read tool in the Coin MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on cache_stats? +

Register the Coin 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 Coin. 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 Coin MCP server (sweetcornna/coin-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.