Get detailed status information for a specific monitor, including
AI agents call get_monitor_status to retrieve information from MCP Datadog Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves monitoring status data without creating, modifying, deleting, or executing operations. The 'get_' prefix and read-only nature of querying monitor status confirms it as a Read category tool. Low severity due to lack of side effects; information disclosure alone presents minimal risk compared to tools that modify state or trigger actions.
From the tool's definition Tool name 'get_monitor_status' and description indicate retrieval of 'detailed status information for a specific monitor' with no modification or deletion capabilities mentioned.
Attacks that exploit this kind of access
Get detailed status information for a specific monitor, including. It is categorised as a Read tool in the MCP Datadog Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Datadog Server MCP server in PolicyLayer and add a rule for get_monitor_status: 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 MCP Datadog Server. Nothing to install.
get_monitor_status 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_monitor_status 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_monitor_status. 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_monitor_status is provided by the MCP Datadog Server MCP server (micaelmalta/mcp-server-datadog). 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 →