New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

get_cache_stats

Get cache statistics from the IntelliRecon AI server.

SERVERIntellirecon Console SOURCEdokotela021/intellirecon-console
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/intellirecon-console/get-cache-stats.md

What get_cache_stats does on Intellirecon Console

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

Why get_cache_stats is rated Low

This tool retrieves and queries statistics about cache behavior. It performs no writes, deletions, code execution, or financial operations. It is purely a read operation on diagnostic/operational data. The low severity reflects minimal blast radius—even if an AI agent misuses it, the worst outcome is viewing cache metrics, which poses no risk to system integrity, security, or data.

From the tool's definition Tool name is 'get_cache_stats' and description states it 'Get[s] cache statistics from the IntelliRecon AI server.' This is purely informational—retrieving statistical metadata about cache performance with no mutation or side effects.

Questions about get_cache_stats

What does the get_cache_stats tool do? +

Get cache statistics from the IntelliRecon AI server. It is categorised as a Read tool in the Intellirecon Console MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_cache_stats? +

Register the Intellirecon Console 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 Intellirecon Console. 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 Intellirecon Console MCP server (dokotela021/intellirecon-console). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Intellirecon Console, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Intellirecon Console's. Pull the full record:

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.