execute_promql_query · Awslabs Valkey MCP: Risk & Policy

WHAT IT DOES

What execute_promql_query does on Awslabs Valkey

AI agents invoke execute_promql_query to trigger actions in Awslabs Valkey. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why execute_promql_query needs a policy

PromQL query execution can access, aggregate, and process data from the underlying database, and depending on implementation, could trigger side effects or access sensitive metrics. The 'execute' verb paired with a query language interpreter places this in the Execute category. Without documentation clarifying sandboxing or read-only constraints, we must assume execution of external operations.

From the tool's definition Tool name is 'execute_promql_query', which indicates execution of a query language (PromQL). The description is empty, but the name and context (ElastiCache/MemoryDB server) indicate this tool runs arbitrary PromQL queries against a Valkey/Redis instance.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

execute_promql_query Rate-limited

execute_promql_query stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "execute_promql_query": {
      "limits": [
        {
          "counter": "execute_promql_query_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Awslabs Valkey, so you can run agents against it safely.

FAQ

Questions about execute_promql_query

What does the execute_promql_query tool do? +

execute_promql_query. It is categorised as a Execute tool in the Awslabs Valkey MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on execute_promql_query? +

Register the Awslabs Valkey MCP server in PolicyLayer and add a rule for execute_promql_query: 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.

What risk level is execute_promql_query? +

execute_promql_query is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit execute_promql_query? +

Yes. Add a rate_limit block to the execute_promql_query 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.

How do I block execute_promql_query completely? +

Set action: deny in the PolicyLayer policy for execute_promql_query. 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.

What MCP server provides execute_promql_query? +

execute_promql_query 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.