run_query

THE RISK

High Risk

This tool likely executes tree-sitter queries or similar code analysis operations whose effects depend on the query arguments provided by the user/AI. While read-only in intent, 'run_query' is categorized as Execute rather than Read because: (1) query execution can trigger complex parsing/traversal of code with non-trivial computational side effects, (2) tree-sitter queries can be crafted to extract sensitive…

From the tool's definition Tool name 'run_query' combined with server context of 'code analysis' and sibling tools like 'build_query' and 'analyze_*' indicates execution of constructed queries against codebases.

Documented attack patterns abuse exactly the kind of access run_query gives an agent:

HOW TO CONTROL RUN_QUERY

PolicyLayer is an MCP gateway — it sits between your AI agents and Tree Sitter, and nothing reaches the server without passing your rules. This is the rule we recommend for run_query:

policy.json

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

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.

Create a free account and register Tree Sitter — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

RATE-LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

More Tree Sitter tools

Destructive clear_cache Clear the parse tree cache. Args: project: Optional project to clear Destructive remove_project_tool Remove a registered project. Args: name: Project name Return Execute build_query build_query Write configure Configure the server. Args: config_path: Path to YAML config file Write register_project_tool Register a project directory for code exploration. Args: path: Path t Read adapt_query Adapt a query from one language to another. Args: query: Original que Read analyze_complexity Analyze code complexity. Args: project: Project name file Read analyze_project Analyze overall project structure. Args: project: Project name

All 26 Tree Sitter tools →

Execute tools on other servers

Frida Game Hacking MCP remove_breakpoint Procmon request_elevation WireMCP capture_packets Pentest Ai run_probe

Go deeper

High-risk tools in Tree Sitter → Every high-risk tool this server exposes, in one view.
All high-risk MCP tools → Every high-risk tool across the catalogue, and the policy pattern that contains them.
The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

What does the run_query tool do? +

run_query. It is categorised as a Execute tool in the Tree Sitter 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 Tree Sitter 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 Tree Sitter. 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 Tree Sitter MCP server (wrale/mcp-server-tree-sitter). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Tree Sitter tool call.

Deterministic rules across all 26 Tree Sitter tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

GOVERN TREE SITTER →

Free to start. No card required.

26 Tree Sitter tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// WHAT RUN_QUERY ON TREE SITTER DOES

// THE RISK

// HOW TO CONTROL RUN_QUERY

// EXPLORE