Reports the bundled offline data directory, the writable user cache directory, sizes, file counts, and whether the server is running in offline mode (ISM_MCP_OFFLINE).
AI agents call cache_info to retrieve information from ISM MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool purely retrieves and reports configuration and cache metadata without side effects. It enables introspection of the server's cached data state but cannot modify, delete, or execute any operations. The information returned could be useful for diagnostics but poses minimal risk if accessed by an AI agent.
From the tool's definition Tool 'cache_info' reports metadata about cached data directories, sizes, and operational status. The description indicates it only provides information retrieval about the cache state: 'Reports the bundled offline data directory, the writable user cache…
Attacks that exploit this kind of access
Reports the bundled offline data directory, the writable user cache directory, sizes, file counts, and whether the server is running in offline mode (ISM_MCP_OFFLINE). It is categorised as a Read tool in the ISM MCP Server MCP Server, which means it retrieves data without modifying state.
Register the ISM MCP Server MCP server in PolicyLayer and add a rule for cache_info: 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 ISM MCP Server. Nothing to install.
cache_info is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the cache_info 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.
Set action: deny in the PolicyLayer policy for cache_info. 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.
cache_info is provided by the ISM MCP Server MCP server (rusticeagle/ism-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the 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 →