// MCP TOOL REFERENCE

run_query

Execute a SurrealQL query against the database

Accepts freeform code/query input (query)

Part of the Devtools MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

// WHEN AI AGENTS USE THIS TOOL

AI agents invoke run_query to trigger processes or run actions in Devtools. Execute operations can have side effects beyond the immediate call -- triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.

// WHY ENFORCE A POLICY ON RUN_QUERY

run_query can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.

// RECOMMENDED POLICY

Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.

devtools.yaml

tools:
  run_query:
    rules:
      - action: allow
        rate_limit:
          max: 10
          window: 60
        validate:
          required_args: true

See the full Devtools policy for all 11 tools.

// DETAILS

Tool Name run_query

Category Execute

MCP Server Devtools MCP Server

Risk Level High

// MORE DEVTOOLS TOOLS

Destructive clear_history Destructive delete_table_row Write update_table_row Read get_active_queries Read get_auth_state Read get_events Read get_state Read get_table_data

View all 11 tools →

// WHAT CAN GO WRONG

Agents calling execute-class tools like run_query have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

// OTHER EXECUTE TOOLS ACROSS MCP SERVERS

Other tools in the Execute risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

Atv build_stake_tx Atv build_unstake_tx Acdp start_local Pentagonal pentagonal_audit Pentagonal pentagonal_compile ACR — Agent Composition Records orient_me

// IN CONTEXT OF HIGH RISK

run_query is one of the high-risk operations in Devtools. For the full severity-focused view — only the high-risk tools with their recommended policies — see the breakdown for this server, or browse all high-risk tools across every MCP server.

// RELATED READING

// FAQ

What does the run_query tool do? +

Execute a SurrealQL query against the database. It is categorised as a Execute tool in the Devtools 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? +

Add a rule in your Intercept YAML policy under the tools section for run_query. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Devtools MCP server.

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 Intercept 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 Intercept 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 Devtools MCP server (@spooky-sync/devtools-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

run_query

Let agents act without letting them run wild.