AI agents call dbt_ls to retrieve information from dbt CLI MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'dbt ls' CLI command lists dbt resources (models, tests, sources, etc.) in a project without modifying any data or state. This is a read-only operation. Confidence is slightly reduced due to the empty description, but the naming convention and dbt CLI knowledge strongly support this classification.
From the tool's definition Tool name 'dbt_ls' strongly suggests a list/directory operation, analogous to the Unix 'ls' command. Description is empty and uninformative.
Documented attack patterns abuse exactly the kind of access dbt_ls 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_ls:
{
"version": "1",
"default": "deny",
"tools": {
"dbt_ls": {}
}
}dbt_ls is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
dbt_ls. It is categorised as a Read tool in the dbt CLI MCP Server MCP Server, which means it retrieves data without modifying state.
Register the dbt CLI MCP Server MCP server in PolicyLayer and add a rule for dbt_ls: 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_ls is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the dbt_ls 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_ls. 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_ls 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.