Create a new Datadog monitor
AI agents use create_monitor to create or update resources in Datadog MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Datadog MCP Server environment.
Creating a monitor in Datadog is a reversible operation that modifies system state by adding monitoring rules. While it could trigger alerting behavior and impact notifications, it does not execute arbitrary code, delete data, or move money. The monitor can be modified or deleted afterward. This qualifies as Write—data creation without side effects that cannot be undone.
From the tool's definition Tool name 'create_monitor' and description 'Create a new Datadog monitor' indicate a create operation that adds new configuration to Datadog.
Attacks that exploit this kind of access
Create a new Datadog monitor. It is categorised as a Write tool in the Datadog MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Datadog MCP Server MCP server in PolicyLayer and add a rule for 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 Datadog MCP Server. Nothing to install.
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 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 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.
create_monitor is provided by the Datadog MCP Server MCP server (ppandrangi/datadog-mcp). 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 →