datadog_list_monitors
AI agents call datadog_list_monitors to retrieve information from Integrations MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
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
datadog_list_monitors. It is categorised as a Read tool in the Integrations MCP MCP Server, which means it retrieves data without modifying state.
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.
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 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.
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 →