Get a comprehensive user guide on how to use the dbt Semantic Layer MCP Server tools. Use this tool to understand the available tools, their parameters, and see workflow examples.
AI agents call get_documentation to retrieve information from dbt Semantic Layer MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves static documentation/help content. It has no side effects, does not query databases, execute code, modify data, or trigger external operations. It is purely informational and falls squarely under the 'Read' category with minimal security risk.
From the tool's definition Tool description states 'Get a comprehensive user guide' and 'understand the available tools' - classic documentation retrieval with no data modification or external operations
Documented attack patterns abuse exactly the kind of access get_documentation gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and dbt Semantic Layer MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_documentation:
{
"version": "1",
"default": "deny",
"tools": {
"get_documentation": {}
}
}get_documentation 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.
Get a comprehensive user guide on how to use the dbt Semantic Layer MCP Server tools. Use this tool to understand the available tools, their parameters, and see workflow examples. It is categorised as a Read tool in the dbt Semantic Layer MCP Server MCP Server, which means it retrieves data without modifying state.
Register the dbt Semantic Layer MCP Server MCP server in PolicyLayer and add a rule for get_documentation: 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 Semantic Layer MCP Server. Nothing to install.
get_documentation 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 get_documentation 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 get_documentation. 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.
get_documentation is provided by the dbt Semantic Layer MCP Server MCP server (tommybez/dbt-semantic-layer-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from dbt Semantic Layer 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.
4 dbt Semantic Layer MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.