server.get_cache_stats

Get caching system statistics and performance metrics

Server ContextForge MCP Gateway jrmatherly/mcp-context-forge
Category Read
Risk class Low
Parameters 00 required

What server.get_cache_stats does on ContextForge MCP Gateway

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

Why server.get_cache_stats needs a policy

This tool queries internal cache performance data for observability purposes. It retrieves information without modifying, executing code, deleting data, or affecting external systems. The blast radius of misuse is minimal—an AI agent could only over-call the endpoint or leak timing information about cache behavior. No configuration changes, data mutations, or external operations are possible.

From the tool's definition Tool name and description indicate retrieval of statistics and metrics: 'Get caching system statistics and performance metrics'. The verb 'Get' and nouns 'statistics' and 'metrics' denote read-only data retrieval with no side effects.

Questions about server.get_cache_stats

What does the server.get_cache_stats tool do? +

Get caching system statistics and performance metrics. It is categorised as a Read tool in the ContextForge MCP Gateway MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on server.get_cache_stats? +

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

What risk level is server.get_cache_stats? +

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

Can I rate-limit server.get_cache_stats? +

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

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

server.get_cache_stats is provided by the ContextForge MCP Gateway MCP server (jrmatherly/mcp-context-forge). 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.