Search Datadog logs with a query and time range
AI agents call search_logs to retrieve information from Datadog Logs 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 and queries existing log data from Datadog without creating, modifying, or deleting records. The capability to search logs can expose sensitive information (application errors, user data, credentials in logs, internal system details) if misused by an AI agent, which justifies 'medium' severity. Confidence is high because the description clearly indicates a read-only search operation.
From the tool's definition Tool name is 'search_logs' and description states 'Search Datadog logs with a query and time range' — core function is retrieval and querying of log data with no mention of modification, deletion, or execution capabilities.
Attacks that exploit this kind of access
Search Datadog logs with a query and time range. It is categorised as a Read tool in the Datadog Logs MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Datadog Logs MCP Server MCP server in PolicyLayer and add a rule for search_logs: 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 Logs MCP Server. Nothing to install.
search_logs 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_logs 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_logs. 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_logs is provided by the Datadog Logs MCP Server MCP server (rezo8/columbo). 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 →