Trace a request flow across services. Pass a trace_id directly, or use filters to find matching logs and automatically extract traces from them.
AI agents call trace_request to retrieve information from Logs Sieve without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only operation on log infrastructure. It retrieves trace data and queries existing logs to display request flows across services. There are no side effects, data modifications, code execution, or irreversible actions. The blast radius of misuse is minimal—an attacker could only view logs they shouldn't access, not modify or delete them. This is a classic 'Read' category tool.
From the tool's definition Tool description states 'Trace a request flow across services' and 'find matching logs and automatically extract traces from them'. The verb 'trace' and 'find' indicate querying/retrieving log data.
Attacks that exploit this kind of access
Trace a request flow across services. Pass a trace_id directly, or use filters to find matching logs and automatically extract traces from them. It is categorised as a Read tool in the Logs Sieve MCP Server, which means it retrieves data without modifying state.
Register the Logs Sieve MCP server in PolicyLayer and add a rule for trace_request: 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 Logs Sieve. Nothing to install.
trace_request 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 trace_request 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 trace_request. 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.
trace_request is provided by the Logs Sieve MCP server (oluwatunmise-olat/mcp-server-logs-sieve). 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 →