get_redis_cache_stats

A read tool on the Mcpg MCP server.

SERVERMcpg SOURCEpypi:mcpg

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-devopam-mcpg/get-redis-cache-stats.md

WHAT IT DOES

What get_redis_cache_stats does on Mcpg

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

RISK

Why get_redis_cache_stats is rated Low

The tool name contains 'get_', which is a strong indicator of read-only retrieval semantics. Cache statistics queries are inherently non-mutating operations that retrieve monitoring/diagnostic information. The absence of a description lowers confidence slightly, but the tool name strongly suggests this retrieves cache performance metrics without modifying any state.

From the tool's definition Tool name 'get_redis_cache_stats' indicates retrieval of cache statistics; no description provided but naming pattern suggests a read-only query operation.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_redis_cache_stats safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Mcpg, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_redis_cache_stats, this is the rule to start with:

get_redis_cache_stats Allowed

get_redis_cache_stats is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

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

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Mcpg, apply this rule, and every get_redis_cache_stats call is checked against it from then on.

FAQ

Questions about get_redis_cache_stats

What does the get_redis_cache_stats tool do? +

get_redis_cache_stats is a read tool on the Mcpg MCP server. It is categorised as a Read tool in the Mcpg MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_redis_cache_stats? +

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

What risk level is get_redis_cache_stats? +

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

Can I rate-limit get_redis_cache_stats? +

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

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

get_redis_cache_stats is provided by the Mcpg MCP server (pypi:mcpg). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Mcpg, and thousands of servers like it.

This server

All 252 Mcpg tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →