submit_trace_location · Triage Agent MCP: Risk & Policy

WHAT IT DOES

What submit_trace_location does on Triage Agent

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

WHY IT NEEDS A POLICY

Why submit_trace_location needs a policy

This tool submits/records analysis results (file path and line range) from stack trace triage. It creates or logs data in a reversible manner without deleting, executing arbitrary code, or moving money. The submission is part of a guided workflow and represents a write operation capturing the agent's findings.

From the tool's definition Tool description states 'Submit the file path and line range' - this is a submission action that records or stores data about trace location analysis as part of the triage workflow.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

submit_trace_location Rate-limited

submit_trace_location 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": {
    "submit_trace_location": {
      "limits": [
        {
          "counter": "submit_trace_location_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 Triage Agent, so you can run agents against it safely.

FAQ

Questions about submit_trace_location

What does the submit_trace_location tool do? +

Step 2 of 2. Submit the file path and line range you identified from the stack trace. It is categorised as a Write tool in the Triage Agent MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on submit_trace_location? +

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

What risk level is submit_trace_location? +

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

Can I rate-limit submit_trace_location? +

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

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

submit_trace_location is provided by the Triage Agent MCP server (rahulnayanegali/triage-agent-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.