run_query · Awslabs Valkey MCP: Risk & Policy

WHAT IT DOES

What run_query does on Awslabs Valkey

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

SQL query execution is classified as Execute because it triggers external operations (database queries) whose effects are entirely dependent on the arguments (the SQL statement provided). While some SQL queries might be read-only (Select), the tool permits arbitrary SQL execution without restriction, so must be treated as Execute.

From the tool's definition Tool is named 'run_query' and description states it can 'Run a SQL query against Microsoft SQL Server'. The ability to execute arbitrary SQL queries allows execution of CREATE, INSERT, UPDATE, DELETE, DROP, and other DML/DDL statements whose effects depend on…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_query Rate-limited

run_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": {
    "run_query": {
      "limits": [
        {
          "counter": "run_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 run_query

What does the run_query tool do? +

Run a SQL query against Microsoft SQL Server. 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 run_query? +

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

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

Can I rate-limit run_query? +

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

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

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