ingest_agent_log_file · State Trace MCP: Risk & Policy

WHAT IT DOES

What ingest_agent_log_file does on State Trace

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

WHY IT NEEDS A POLICY

Why ingest_agent_log_file needs a policy

The tool ingests/imports log file data into the system, creating or modifying stored data (trajectory records). This is a Write operation as it persists new data into the working memory graph. Severity is medium because an AI agent could ingest malicious or corrupt trajectory data affecting the agent's working memory state, but it does not irreversibly destroy existing data.

From the tool's definition Ingest an agent trajectory (SWE-agent .traj, OpenHands JSON, or ...)

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

ingest_agent_log_file Rate-limited

ingest_agent_log_file 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": {
    "ingest_agent_log_file": {
      "limits": [
        {
          "counter": "ingest_agent_log_file_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 State Trace, so you can run agents against it safely.

FAQ

Questions about ingest_agent_log_file

What does the ingest_agent_log_file tool do? +

Ingest an agent trajectory (SWE-agent .traj, OpenHands JSON, or. It is categorised as a Write tool in the State Trace MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on ingest_agent_log_file? +

Register the State Trace MCP server in PolicyLayer and add a rule for ingest_agent_log_file: 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 State Trace. Nothing to install.

What risk level is ingest_agent_log_file? +

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

Can I rate-limit ingest_agent_log_file? +

Yes. Add a rate_limit block to the ingest_agent_log_file 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 ingest_agent_log_file completely? +

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

ingest_agent_log_file is provided by the State Trace MCP server (agent-pattern-labs/state-trace). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// THE FULL RECORD

ingest_agent_log_file is one line of State Trace's registry record.

The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.

Teams ship this data inside their own products. See what a licence covers →