query_metrics
Retrieve metrics data from Datadog
Part of the Datadog MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
WHEN AI AGENTS USE THIS TOOL
AI agents call query_metrics to retrieve information from Datadog without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions — but you may still want rate limits to control API costs.
WHY ENFORCE A POLICY ON QUERY_METRICS
Even though query_metrics only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
RECOMMENDED POLICY
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
tools:
query_metrics:
rules:
- action: allowSee the full Datadog policy for all 20 tools.
DETAILS
MORE DATADOG TOOLS
get_active_hosts_count Read get_dashboard Read get_incident Read get_logs Read get_monitors Read get_rum_applications Read get_rum_events Read get_rum_grouped_event_count Read SIMILAR READ TOOLS ON OTHER SERVERS
list_bases Airtable list_tables Airtable list_records Airtable get_record Airtable search_records Airtable search Amplitude RELATED READING
FREQUENTLY ASKED QUESTIONS
What does the query_metrics tool do?
Retrieve metrics data from Datadog. It is categorised as a Read tool in the Datadog MCP Server, which means it retrieves data without modifying state.
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 Datadog MCP server.
What risk level is query_metrics?
query_metrics is a Read tool with low risk. Read-only tools are generally safe to allow by default.
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 Datadog MCP server (winor30/mcp-server-datadog). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
ENFORCE POLICIES ON DATADOG
Open source. One binary. Zero dependencies.