getCollectionStats
AI agents call getCollectionStats to retrieve information from Amazon ElastiCache Memcached MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The name indicates a stats-retrieval operation (Read category). ElastiCache Memcached stats queries are non-destructive observational actions. Severity is low because statistics retrieval has no blast radius—it merely exposes cache performance metrics. Confidence is moderate (0.7) due to missing description, but the name strongly suggests a read operation.
From the tool's definition Tool name 'getCollectionStats' suggests retrieval of statistical data from a collection, consistent with querying/monitoring operations. Description is empty, limiting certainty.
Attacks that exploit this kind of access
getCollectionStats. It is categorised as a Read tool in the Amazon ElastiCache Memcached MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Amazon ElastiCache Memcached MCP Server MCP server in PolicyLayer and add a rule for getCollectionStats: 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 Amazon ElastiCache Memcached MCP Server. Nothing to install.
getCollectionStats 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 getCollectionStats 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 getCollectionStats. 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.
getCollectionStats is provided by the Amazon ElastiCache Memcached MCP Server MCP server (awslabs.memcached-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.