get_metrics
AI agents call get_metrics 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.
The tool retrieves metrics without modifying, executing operations, or affecting data state. Although the description is empty (lowering confidence slightly), the name and server context clearly indicate a read-only query operation. Metrics retrieval has minimal blast radius since it cannot alter system state or trigger external actions beyond returning data.
From the tool's definition Tool name 'get_metrics' indicates data retrieval. The Amazon ElastiCache/MemoryDB context suggests this tool queries performance and operational metrics from the cache service, consistent with monitoring and observability tasks.
Attacks that exploit this kind of access
get_metrics. 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 get_metrics: 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.
get_metrics 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_metrics 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_metrics. 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_metrics 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.