get_cache_stats

Get cache statistics from the API server.

SERVERNyxstrike SOURCECommonHuman-Lab/nyxstrike

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/nyxstrike/get-cache-stats.md

WHAT IT DOES

What get_cache_stats does on Nyxstrike

AI agents call get_cache_stats to retrieve information from Nyxstrike 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_cache_stats is rated Low

This tool performs a simple read operation to retrieve statistical information about cache performance. It retrieves data without side effects, triggering no code execution, financial transactions, or destructive actions. Within the context of a penetration testing platform, querying cache statistics poses minimal risk when isolated from offensive capabilities.

From the tool's definition Tool name 'get_cache_stats' and description 'Get cache statistics from the API server' indicate a retrieval operation with no modification or execution capability.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs get_cache_stats safely

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

get_cache_stats Allowed

get_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_cache_stats": {}
  }
}

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

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

FAQ

Questions about get_cache_stats

What does the get_cache_stats tool do? +

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

How do I enforce a policy on get_cache_stats? +

Register the Nyxstrike 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 Nyxstrike. 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 Nyxstrike MCP server (CommonHuman-Lab/nyxstrike). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Nyxstrike, and thousands of servers like it.

This server

All 221 Nyxstrike 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 →