AI agents call lithtrix_trace_get to retrieve information from Lithtrix without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves audit/trace data about a task without modifying, deleting, or executing anything. It is a read-only query operation with no side effects. The access restriction to task participants further limits blast radius. Severity is low because audit logs typically contain historical metadata rather than sensitive operational data that could cause immediate harm if exposed.
From the tool's definition Tool description explicitly states 'Read task audit trace' and uses GET HTTP method. The action is retrieval-only with access control ('Task participant only').
Attacks that exploit this kind of access
Read task audit trace (GET /v1/tasks/{task_id}/trace). Task participant only. It is categorised as a Read tool in the Lithtrix MCP Server, which means it retrieves data without modifying state.
Register the Lithtrix MCP server in PolicyLayer and add a rule for lithtrix_trace_get: 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 Lithtrix. Nothing to install.
lithtrix_trace_get 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 lithtrix_trace_get 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 lithtrix_trace_get. 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.
lithtrix_trace_get is provided by the Lithtrix MCP server (lithtrix/lithtrix-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 →