AI agents call swarm_cache_stats to retrieve information from Mcp Swarm without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries statistics about a Redis cache. It performs a read-only operation with no side effects—it does not create, modify, delete, or execute code. The action is purely informational, collecting cache performance metrics. This falls clearly into the Read category with low severity since cache statistics exposure has minimal security impact.
From the tool's definition Tool name 'swarm_cache_stats' and description '获取 Redis 缓存统计信息' (Get Redis cache statistics) indicate a retrieval operation that queries cache metrics without modifying state.
Attacks that exploit this kind of access
获取 Redis 缓存统计信息。. It is categorised as a Read tool in the Mcp Swarm MCP Server, which means it retrieves data without modifying state.
Register the Mcp Swarm MCP server in PolicyLayer and add a rule for swarm_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 Mcp Swarm. Nothing to install.
swarm_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 swarm_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 swarm_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.
swarm_cache_stats is provided by the Mcp Swarm MCP server (moselu/mcp-swarm). 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 →