get-metric-statistics
AI agents call get-metric-statistics 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 name follows the standard pattern of read operations ('get-*') and is consistent with AWS CloudWatch metric retrieval functions, which retrieve statistics without modifying state. The empty description lowers confidence slightly, but the semantic meaning of 'get-metric-statistics' aligns clearly with Read category behavior—querying and retrieving monitoring data has no side effects.
From the tool's definition Tool name 'get-metric-statistics' indicates retrieval of metric data. No description provided to confirm behavior, but the verb 'get' and the stateless nature of metric queries strongly suggest read-only data retrieval.
Attacks that exploit this kind of access
get-metric-statistics. 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-metric-statistics: 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-metric-statistics 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-metric-statistics 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-metric-statistics. 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-metric-statistics 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.