AI agents invoke dbt_build to trigger actions in dbt CLI MCP Server. 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.
dbt build combines dbt run and dbt test operations, executing data transformation logic that modifies database state. While not Destructive by itself (it creates/updates tables rather than dropping them), it is Execute-level because it triggers external database operations whose effects depend on the dbt project configuration and model definitions.
From the tool's definition Tool name 'dbt_build' with no description; dbt build is a dbt command that executes data transformations (runs models, tests, and snapshots); sibling tools include dbt_run, dbt_test, dbt_seed which are known Execute operations in dbt workflows.
Documented attack patterns abuse exactly the kind of access dbt_build gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and dbt CLI MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for dbt_build:
{
"version": "1",
"default": "deny",
"tools": {
"dbt_build": {
"limits": [
{
"counter": "dbt_build_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}dbt_build 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.
Free to start. No card required.
dbt_build. It is categorised as a Execute tool in the dbt CLI MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the dbt CLI MCP Server MCP server in PolicyLayer and add a rule for dbt_build: 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 dbt CLI MCP Server. Nothing to install.
dbt_build is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the dbt_build 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.
Set action: deny in the PolicyLayer policy for dbt_build. 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.
dbt_build is provided by the dbt CLI MCP Server MCP server (mammothgrowth/dbt-cli-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from dbt CLI MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
9 dbt CLI MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.