Get statistics about the MTA:SA documentation cache.
AI agents call get_cache_stats to retrieve information from MTA:SA Documentation MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves cache statistics, which is a read-only operation. It does not modify, delete, or execute any operations—it only queries and returns information about the state of the documentation cache. This aligns with the Read category definition of retrieves or queries data with no side effects.
From the tool's definition Tool name is 'get_cache_stats' and description states it 'Get statistics about the MTA:SA documentation cache.' This is purely a retrieval operation that queries cache metadata with no side effects.
Attacks that exploit this kind of access
Get statistics about the MTA:SA documentation cache. It is categorised as a Read tool in the MTA:SA Documentation MCP Server MCP Server, which means it retrieves data without modifying state.
Register the MTA:SA Documentation MCP Server 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 MTA:SA Documentation MCP Server. Nothing to install.
get_cache_stats 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 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.
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.
get_cache_stats is provided by the MTA:SA Documentation MCP Server MCP server (mtasa-docs-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 →