getCollectionStats
AI agents call getCollectionStats to retrieve information from Awslabs Valkey without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves statistical information about a collection in ElastiCache/MemoryDB, consistent with monitoring and observability use cases. No modification, deletion, code execution, or financial impact is implied. The blast radius of misuse is minimal—returning stats cannot harm data or systems.
From the tool's definition Tool name 'getCollectionStats' indicates retrieval of statistics/metrics about a collection with no side effects. The 'get' prefix is characteristic of Read operations.
Attacks that exploit this kind of access
getCollectionStats. It is categorised as a Read tool in the Awslabs Valkey MCP Server, which means it retrieves data without modifying state.
Register the Awslabs Valkey 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 Awslabs Valkey. 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 Awslabs Valkey MCP server (awslabs.valkey-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.