get_metric_data
AI agents call get_metric_data 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 metrics from ElastiCache/MemoryDB without modifying state. Even if it queries time-series or performance data, it has no side effects and poses minimal risk of misuse by an AI agent. Low severity due to read-only nature and typical benign use case of accessing operational metrics.
From the tool's definition Tool name 'get_metric_data' indicates retrieval of metric data without modification. Empty description limits certainty, but the name strongly suggests a query operation returning monitoring/observability data.
Attacks that exploit this kind of access
get_metric_data. 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_data: 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_data 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_data 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_data. 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_data 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.