fetch_metrics · dbt Semantic Layer MCP Server MCP

WHAT IT DOES

What fetch_metrics does on dbt Semantic Layer MCP Server

AI agents call fetch_metrics 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.

THE RISK

Low Risk

Why fetch_metrics needs a policy

This tool queries and retrieves metric definitions from the dbt Semantic Layer. It is a read-only operation that does not create, modify, delete, or execute code. The action is purely data retrieval, which carries minimal risk if misused by an AI agent.

From the tool's definition Tool name 'fetch_metrics' and description 'Fetches metrics from the semantic layer' indicate a retrieval operation with no modification or deletion of data.

Documented attack patterns abuse exactly the kind of access fetch_metrics gives an agent:

POLICY

How to control fetch_metrics

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 fetch_metrics:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "fetch_metrics": {}
  }
}

fetch_metrics is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register dbt Semantic Layer MCP Server — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More dbt Semantic Layer MCP Server tools

Execute create_query Creates a query to the semantic layer. Read fetch_query_result Fetches the results of a query from the semantic layer. You have to poll this tool until t Read get_documentation Get a comprehensive user guide on how to use the dbt Semantic Layer MCP Server tools. Use

All 4 dbt Semantic Layer MCP Server tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about fetch_metrics

What does the fetch_metrics tool do? +

Fetches metrics from the semantic layer. It is categorised as a Read tool in the dbt Semantic Layer MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on fetch_metrics? +

Register the dbt Semantic Layer MCP Server MCP server in PolicyLayer and add a rule for fetch_metrics: 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.

What risk level is fetch_metrics? +

fetch_metrics is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit fetch_metrics? +

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

How do I block fetch_metrics completely? +

Set action: deny in the PolicyLayer policy for fetch_metrics. 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 fetch_metrics? +

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

Enforce policy on every dbt Semantic Layer MCP Server tool call.

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.

CHECK YOUR STACK →

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.