query_metrics
Execute metric queries with filtering and grouping
Part of the dbt MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
WHEN AI AGENTS USE THIS TOOL
AI agents invoke query_metrics to trigger processes or run actions in dbt. Execute operations can have side effects beyond the immediate call — triggering builds, sending notifications, or starting workflows. Rate limits and argument validation are essential to prevent runaway execution.
WHY ENFORCE A POLICY ON QUERY_METRICS
query_metrics can trigger processes with real-world consequences. An uncontrolled agent might start dozens of builds, send mass notifications, or kick off expensive compute jobs. Intercept enforces rate limits and validates arguments to keep execution within safe bounds.
RECOMMENDED POLICY
Execute tools trigger processes. Rate-limit and validate arguments to prevent unintended side effects.
tools:
query_metrics:
rules:
- action: allow
rate_limit:
max: 10
window: 60
validate:
required_args: trueSee the full dbt policy for all 48 tools.
DETAILS
MORE DBT TOOLS
execute_sql Execute text_to_sql Execute build Execute compile Execute docs Execute parse Execute run Execute show Execute SIMILAR EXECUTE TOOLS ON OTHER SERVERS
call-actor Apify boot_simulator Appium setup_wda Appium install_wda Appium auth0_deploy_action Auth0 auth0_publish_form Auth0 RELATED READING
FREQUENTLY ASKED QUESTIONS
What does the query_metrics tool do?
Execute metric queries with filtering and grouping. It is categorised as a Execute tool in the dbt MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
How do I enforce a policy on query_metrics?
Add a rule in your Intercept YAML policy under the tools section for query_metrics. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the dbt MCP server.
What risk level is query_metrics?
query_metrics is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Can I rate-limit query_metrics?
Yes. Add a rate_limit block to the query_metrics rule in your Intercept 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 query_metrics completely?
Set action: deny in the Intercept policy for query_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 query_metrics?
query_metrics is provided by the dbt MCP server (dbt-labs/dbt-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
ENFORCE POLICIES ON DBT
Open source. One binary. Zero dependencies.