AI agents use datadog_create_monitor to create or update resources in UnClick — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your UnClick environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
name | string | Yes | Monitor name |
tags | array | — | Tags to attach to the monitor |
type | string | — | Monitor type (e.g. metric alert, service check, event alert) |
query | string | Yes | Monitor query expression |
api_key | string | Yes | Datadog API key |
app_key | string | Yes | Datadog Application key |
message | string | — | Notification message |
priority | number | — | Monitor priority (1-5) |
Parameters from the server's own tool schema.
This tool creates a new monitoring alert in Datadog, which is a reversible write operation. An AI agent misusing this could create spurious alerts or alert fatigue, but the action is not destructive (alerts can be deleted), not financial, and does not execute arbitrary code. The blast radius is medium—unwanted alerts could clutter monitoring systems and distract teams, but the core system remains intact.
From the tool's definition Tool name 'datadog_create_monitor' and description 'Create a new Datadog monitor (alert)' indicate creation of a new monitoring/alerting resource.
Risk signalsAccepts freeform code/query input (query) · Handles credentials or secrets (api_key)
Attacks that exploit this kind of access
Create a new Datadog monitor (alert). It is categorised as a Write tool in the UnClick MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
datadog_create_monitor accepts 8 parameters: name, tags, type, query, api_key, app_key, message, priority. Required: name, 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_create_monitor: 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_create_monitor is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the datadog_create_monitor 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_create_monitor. 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_create_monitor 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 →