MCP Tool Reference High Risk

text_to_sql

Generate SQL from natural language

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

WHEN AI AGENTS USE THIS TOOL

AI agents invoke text_to_sql to trigger processes or run actions in dbt. 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 TEXT_TO_SQL

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

dbt.yaml
tools:
  text_to_sql:
    rules:
      - action: allow
        rate_limit:
          max: 10
          window: 60
        validate:
          required_args: true

See the full dbt policy for all 48 tools.

DETAILS

Tool Name

text_to_sql

Category

Execute

MCP Server

dbt MCP Server

Risk Level

High

MORE DBT TOOLS

View all 48 tools →

SIMILAR EXECUTE TOOLS ON OTHER SERVERS

RELATED READING

FREQUENTLY ASKED QUESTIONS

What does the text_to_sql tool do?

Generate SQL from natural language. It is categorised as a Execute tool in the dbt MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on text_to_sql?

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

What risk level is text_to_sql?

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

Can I rate-limit text_to_sql?

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

Set action: deny in the Intercept policy for text_to_sql. 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 text_to_sql?

text_to_sql is provided by the dbt MCP server (dbt-labs/dbt-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

ENFORCE POLICIES ON DBT

Open source. One binary. Zero dependencies.