get_promql_labels
AI agents call get_promql_labels 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 queries and retrieves label information from a monitoring/observability system. Labels in Prometheus are tag-like metadata used to filter and organize metrics. Retrieving labels is a read-only operation with no side effects on the system.
From the tool's definition Tool name 'get_promql_labels' indicates retrieval of Prometheus query language (PromeQL) labels, which are metadata descriptors used in monitoring systems. The 'get_' prefix and plural 'labels' suggest a data retrieval operation without modification.
Attacks that exploit this kind of access
get_promql_labels. 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_promql_labels: 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_promql_labels 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_promql_labels 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_promql_labels. 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_promql_labels 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.