track_error_full · Error Tracker MCP Server MCP

WHAT IT DOES

What track_error_full does on Error Tracker MCP Server

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

WHY IT NEEDS A POLICY

Why track_error_full needs a policy

The tool performs a multi-step workflow that includes finding code owners (Read), retrieving PR information (Read), and crucially, creating JIRA tickets (Write). Since it creates/modifies data in JIRA reversibly, it falls into the Write category. While it orchestrates multiple operations, the most impactful and intentional outcome is ticket creation.

From the tool's definition The tool description states it "create[s] JIRA ticket" and the sibling tool `create_jira_ticket` is present on the server. Creating tickets in JIRA is a write operation that modifies issue tracking state.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

track_error_full Rate-limited

track_error_full 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": {
    "track_error_full": {
      "limits": [
        {
          "counter": "track_error_full_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 Error Tracker MCP Server, so you can run agents against it safely.

FAQ

Questions about track_error_full

What does the track_error_full tool do? +

Complete workflow: find code owner, get PR info, and create JIRA ticket for an error. It is categorised as a Write tool in the Error Tracker MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on track_error_full? +

Register the Error Tracker MCP Server MCP server in PolicyLayer and add a rule for track_error_full: 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 Error Tracker MCP Server. Nothing to install.

What risk level is track_error_full? +

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

Can I rate-limit track_error_full? +

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

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

track_error_full is provided by the Error Tracker MCP Server MCP server (wyccome/mcp-error-tracing). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.