exploit_cache_stats

What exploit_cache_stats does on Jshookmcp

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

Why exploit_cache_stats is rated Low

This tool retrieves cache statistics (hit rate, memory usage, entry count) for diagnostic and monitoring purposes. It performs no modifications, deletions, code execution, or financial operations. While the server context involves 'exploit' development, this specific tool only reads cached metrics, making it a straightforward Read category with low severity—an AI agent cannot cause harm by querying cache statistics.

From the tool's definition Tool description states it 'Get[s] exploit-dev cache statistics including hit rate, memory usage, and entry count' — purely informational retrieval with 'no side effects' beyond querying cache state.

The rule that runs exploit_cache_stats safely

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

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

Questions about exploit_cache_stats