update_monitor · Datadog MCP Server MCP: Risk & Policy

WHAT IT DOES

What update_monitor does on Datadog MCP Server

AI agents use update_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.

WHY IT NEEDS A POLICY

Why update_monitor needs a policy

This tool modifies existing data (monitor configuration) reversibly. While not destructive, updating monitors could cause alerts to fire incorrectly, silence critical notifications, or redirect alerts—affecting system observability and incident response.

From the tool's definition Tool name 'update_monitor' and description 'Update an existing Datadog monitor' indicate modification of existing monitoring configuration. The server supports 'full CRUD operations' including updates to monitors, which are critical alerting infrastructure.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_monitor Rate-limited

update_monitor stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "update_monitor": {
      "limits": [
        {
          "counter": "update_monitor_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Datadog MCP Server, so you can run agents against it safely.

FAQ

Questions about update_monitor

What does the update_monitor tool do? +

Update an existing 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.

How do I enforce a policy on update_monitor? +

Register the Datadog MCP Server MCP server in PolicyLayer and add a rule for update_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.

What risk level is update_monitor? +

update_monitor is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit update_monitor? +

Yes. Add a rate_limit block to the update_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.

How do I block update_monitor completely? +

Set action: deny in the PolicyLayer policy for update_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.

What MCP server provides update_monitor? +

update_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.