Get specific dashboard by ID
AI agents call get_dashboard to retrieve information from Datadog MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves dashboard information without modifying, deleting, or executing operations. It is a straightforward data retrieval operation that returns existing dashboard configuration. The blast radius of misuse is minimal—an agent could view dashboards it shouldn't access, but cannot modify infrastructure or cause data loss. This is purely a Read operation.
From the tool's definition Tool name 'get_dashboard' and description 'Get specific dashboard by ID' indicate a retrieval operation with no side effects. The verb 'Get' and context of querying a specific resource by identifier are characteristic of read-only access patterns.
Attacks that exploit this kind of access
Get specific dashboard by ID. It is categorised as a Read tool in the Datadog MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Datadog MCP Server MCP server in PolicyLayer and add a rule for get_dashboard: 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.
get_dashboard 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 get_dashboard 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 get_dashboard. 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.
get_dashboard 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 →