AI agents call datadog_query_metrics to retrieve information from UnClick without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
to | number | — | End time as Unix timestamp (default: now) |
from | number | — | Start time as Unix timestamp (default: 1 hour ago) |
query | string | Yes | Datadog metric query (e.g. avg:system.cpu.user{*}) |
api_key | string | Yes | Datadog API key |
app_key | string | Yes | Datadog Application key |
Parameters from the server's own tool schema.
This tool retrieves and queries existing metrics data from Datadog. It has no side effects, does not modify data, execute code, delete resources, or commit financial transactions. The blast radius of misuse is minimal — at worst, an agent could access sensitive monitoring metrics or expose system performance data, but cannot change configurations or trigger incidents.
From the tool's definition Tool name contains 'query' and description states 'Query Datadog metrics time-series data' — purely retrieves monitoring data without modification or execution of external operations.
Risk signalsAccepts freeform code/query input (query) · Handles credentials or secrets (api_key)
Attacks that exploit this kind of access
Query Datadog metrics time-series data. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
datadog_query_metrics accepts 5 parameters: to, from, query, api_key, app_key. Required: query, api_key, app_key. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for datadog_query_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 UnClick. Nothing to install.
datadog_query_metrics 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 datadog_query_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.
Set action: deny in the PolicyLayer policy for datadog_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.
datadog_query_metrics is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →