executeQuery · Awslabs Valkey MCP: Risk & Policy

WHAT IT DOES

What executeQuery does on Awslabs Valkey

AI agents invoke executeQuery 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 executeQuery needs a policy

Although described as 'read-only SELECT query', the tool executes arbitrary queries provided as arguments. This represents Execute category because: (1) it runs code (SQL queries) whose effects depend on the supplied 'query' argument, (2) an AI agent could be manipulated into executing unintended queries that bypass the read-only constraint through SQL injection or misuse, and (3) executeQuery permits triggering…

From the tool's definition Tool name 'executeQuery' with description 'Executes a read-only SELECT query against the database' indicates runtime execution of arbitrary database queries.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

executeQuery Rate-limited

executeQuery 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": {
    "executeQuery": {
      "limits": [
        {
          "counter": "executequery_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 executeQuery

What does the executeQuery tool do? +

Executes a read-only SELECT query against the database - args: keyspace, 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 executeQuery? +

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

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

Can I rate-limit executeQuery? +

Yes. Add a rate_limit block to the executeQuery 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 executeQuery completely? +

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

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