datadog_list_monitors

A read tool on the Integrations MCP server.

SERVERIntegrations MCP SOURCEshriram-vasudevan/integrations-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/shriram-vasudevan-integrations-mcp/datadog-list-monitors.md

WHAT IT DOES

What datadog_list_monitors does on Integrations MCP

AI agents call datadog_list_monitors to retrieve information from Integrations MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why datadog_list_monitors is rated Low

The 'list' verb indicates this tool retrieves monitor data from Datadog without modifying anything. However, Datadog monitors often guard critical infrastructure and alerting configurations; unauthorized enumeration of monitors could reveal sensitive deployment and security monitoring details, justifying medium severity. Empty description lowers confidence from high to medium-high.

From the tool's definition Tool name 'datadog_list_monitors' contains 'list', which is a Read operation that retrieves or queries data without side effects. Description is empty, limiting confidence.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs datadog_list_monitors safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Integrations MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For datadog_list_monitors, this is the rule to start with:

datadog_list_monitors Allowed

datadog_list_monitors is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "datadog_list_monitors": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Integrations MCP, apply this rule, and every datadog_list_monitors call is checked against it from then on.

FAQ

Questions about datadog_list_monitors

What does the datadog_list_monitors tool do? +

datadog_list_monitors is a read tool on the Integrations MCP server. It is categorised as a Read tool in the Integrations MCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on datadog_list_monitors? +

Register the Integrations 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 Integrations MCP. Nothing to install.

What risk level is datadog_list_monitors? +

datadog_list_monitors is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit datadog_list_monitors? +

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.

How do I block datadog_list_monitors completely? +

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.

What MCP server provides datadog_list_monitors? +

datadog_list_monitors is provided by the Integrations MCP server (shriram-vasudevan/integrations-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Integrations, and thousands of servers like it.

This server

All 420 Integrations tools →

Across the catalogue

aiva_list_affiliates on AIVA MCP Server →list_circuits on 0gzk →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →