Search logs by OpenTelemetry trace ID to see all logs related to a specific request/transaction.
AI agents call search_by_trace to retrieve information from OpenSearch 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 based on trace ID criteria. It performs a read-only operation that has no side effects on the underlying data. While logs may contain sensitive information, the tool itself is fundamentally a data retrieval mechanism, making it a Read category tool with low severity risk.
From the tool's definition Tool description states 'Search logs by OpenTelemetry trace ID to see all logs related to a specific request/transaction.' The verb 'search' and 'see' indicate retrieval/query operations with no modification or deletion of data.
Attacks that exploit this kind of access
Search logs by OpenTelemetry trace ID to see all logs related to a specific request/transaction. It is categorised as a Read tool in the OpenSearch Logs MCP Server MCP Server, which means it retrieves data without modifying state.
Register the OpenSearch Logs MCP Server MCP server in PolicyLayer and add a rule for search_by_trace: 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 OpenSearch Logs MCP Server. Nothing to install.
search_by_trace 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_by_trace 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_by_trace. 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_by_trace is provided by the OpenSearch Logs MCP Server MCP server (luis-dominguez-stori/mcp). 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 →