datadog_list_dashboards
AI agents call datadog_list_dashboards 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' operation retrieves or enumerates dashboards from Datadog's monitoring platform. This is a passive query with no side effects—it does not create, modify, delete, execute code, or involve financial transactions. Listing dashboards has minimal blast radius if misused by an AI agent, as it only returns metadata about existing monitoring configurations.
From the tool's definition Tool name contains 'list' indicating a retrieval operation that queries existing dashboards without modifying state. The empty description is a limitation, but the 'list' verb is a strong signal of read-only behavior.
Attacks that exploit this kind of access
datadog_list_dashboards. 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_dashboards: 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_dashboards 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_dashboards 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_dashboards. 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_dashboards 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 →