AI agents call datadog_list_monitors 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 |
|---|---|---|---|
name | string | — | Filter monitors by name |
page | number | — | Page number (0-indexed) |
tags | string | — | Comma-separated monitor tags to filter by |
api_key | string | Yes | Datadog API key (DD-API-KEY) |
app_key | string | Yes | Datadog Application key (DD-APPLICATION-KEY) |
page_size | number | — | Monitors per page (max: 1000) |
Parameters from the server's own tool schema.
This tool queries and retrieves monitoring data from Datadog without creating, modifying, deleting, or executing anything. It has minimal blast radius — exposure returns only alert configuration metadata, posing no direct risk to systems or data integrity.
From the tool's definition Tool name includes 'list' and description states 'List Datadog monitors (alerts) with optional name or tag filters' — purely retrieval operation with no modification or execution capability.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
List Datadog monitors (alerts) with optional name or tag filters. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
datadog_list_monitors accepts 6 parameters: name, page, tags, api_key, app_key, page_size. Required: 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_list_monitors: 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_list_monitors 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_list_monitors 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_list_monitors. 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_list_monitors 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 →