AI agents invoke dbt_run 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_run executes transformations that materialize models in a target database—this is an Execute action with external operational effects (data writes to warehouse). While it creates/modifies data (suggesting Write), the primary risk is that execution effects are not easily reversible and depend entirely on model logic.
From the tool's definition Tool name 'dbt_run' executes dbt models/transformations. Based on sibling tools (dbt_build, dbt_compile, dbt_seed, dbt_test) which are all transformation/execution operations, dbt_run is a dbt command that triggers SQL/transformation execution against data…
Documented attack patterns abuse exactly the kind of access dbt_run 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_run:
{
"version": "1",
"default": "deny",
"tools": {
"dbt_run": {
"limits": [
{
"counter": "dbt_run_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}dbt_run 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_run. 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_run: 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_run 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_run 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_run. 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_run 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.