get_language_metrics
AI agents call get_language_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 name indicates a read operation (get) that retrieves language-related metrics. The empty description limits confidence, but the naming pattern aligns with data retrieval. No indication of modification, deletion, or external execution. Classified as Read with low severity due to typical lack of side effects from metric queries. Confidence reduced to 0.6 due to absence of formal documentation.
From the tool's definition Tool name 'get_language_metrics' suggests retrieval of metrics data; no description provided to confirm side effects.
Attacks that exploit this kind of access
get_language_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_language_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_language_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_language_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_language_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_language_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.