lithtrix_trace_append · Lithtrix MCP: Risk & Policy

WHAT IT DOES

What lithtrix_trace_append does on Lithtrix

AI agents use lithtrix_trace_append to create or update resources in Lithtrix — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Lithtrix environment.

WHY IT NEEDS A POLICY

Why lithtrix_trace_append needs a policy

The tool creates new trace event records via HTTP POST, which is a write operation. It appends data to an existing task's trace log, modifying persistent state. Since it 'records only' with no runtime veto, it cannot execute code or cause destructive effects. Misuse could pollute audit/trace logs with false data, making it medium severity.

From the tool's definition 'Append a task trace event (POST /v1/tasks/{task_id}/trace/events). Records only — no runtime veto.'

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

lithtrix_trace_append Rate-limited

lithtrix_trace_append stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "lithtrix_trace_append": {
      "limits": [
        {
          "counter": "lithtrix_trace_append_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Lithtrix, so you can run agents against it safely.

FAQ

Questions about lithtrix_trace_append

What does the lithtrix_trace_append tool do? +

Append a task trace event (POST /v1/tasks/{task_id}/trace/events). Records only — no runtime veto. It is categorised as a Write tool in the Lithtrix MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on lithtrix_trace_append? +

Register the Lithtrix MCP server in PolicyLayer and add a rule for lithtrix_trace_append: 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.

What risk level is lithtrix_trace_append? +

lithtrix_trace_append is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit lithtrix_trace_append? +

Yes. Add a rate_limit block to the lithtrix_trace_append 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.

How do I block lithtrix_trace_append completely? +

Set action: deny in the PolicyLayer policy for lithtrix_trace_append. 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.

What MCP server provides lithtrix_trace_append? +

lithtrix_trace_append 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.