Get detailed information about a specific log entry.
AI agents call get_log_details 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 log data without creating, modifying, or deleting any resources. It is a straightforward read operation with minimal security impact when misused by an AI agent—the worst-case scenario is exposure of log data the agent is already authorized to access.
From the tool's definition Tool name 'get_log_details' and description 'Get detailed information about a specific log entry' indicate a retrieval operation with no modification or deletion of data. The verb 'get' and the context of querying Datadog logs confirm read-only semantics.
Attacks that exploit this kind of access
Get detailed information about a specific log entry. 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_log_details: 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_log_details 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_log_details 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_log_details. 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_log_details 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 →