Search for monitors by name or other criteria. Useful for finding
AI agents call search_monitors 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 is a pure query operation that searches existing monitors in Datadog. It returns matching monitor records (names, IDs, configurations, status) without creating, modifying, deleting, or executing anything. The use case of 'finding' monitors confirms it is a retrieval-only action. No side effects or state changes occur.
From the tool's definition Tool name is 'search_monitors' and description states 'Search for monitors by name or other criteria' — typical read/query operation that retrieves information without modification.
Attacks that exploit this kind of access
Search for monitors by name or other criteria. Useful for finding. 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 search_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 MCP Datadog Server. Nothing to install.
search_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 search_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 search_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.
search_monitors 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 →