Search for events in Datadog. Events can include monitor alerts,
AI agents call search_events 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 and queries event data from Datadog. It has no side effects—it does not create, modify, delete, or execute external operations. It is a straightforward read operation on existing Datadog events, similar to other read-only tools on the server like get_event_details, get_monitor_status, and list_metrics. The blast radius of misuse is low, as an AI agent cannot cause damage by searching events.
From the tool's definition Tool name is 'search_events' and description states 'Search for events in Datadog.' The verb 'search' and context of querying existing events indicates retrieval/query functionality with no modification or deletion.
Attacks that exploit this kind of access
Search for events in Datadog. Events can include monitor alerts,. 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_events: 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_events 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_events 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_events. 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_events 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 →