retrack_shipments · Trackmage MCP Server MCP: Risk & Policy

WHAT IT DOES

What retrack_shipments does on Trackmage MCP Server

AI agents invoke retrack_shipments to trigger actions in Trackmage MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why retrack_shipments needs a policy

Retracking shipments triggers an external operation (re-querying carrier APIs and updating tracking state) rather than simply reading or writing data. It initiates a process whose effects depend on the provided tracking numbers and could affect multiple records simultaneously, making it an Execute-category action.

From the tool's definition 'Retrack multiple shipments by tracking numbers' — triggers an external re-tracking operation against the TrackMage API for multiple shipments

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

retrack_shipments Rate-limited

retrack_shipments stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "retrack_shipments": {
      "limits": [
        {
          "counter": "retrack_shipments_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about retrack_shipments

What does the retrack_shipments tool do? +

Retrack multiple shipments by tracking numbers. It is categorised as a Execute tool in the Trackmage MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on retrack_shipments? +

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

What risk level is retrack_shipments? +

retrack_shipments is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit retrack_shipments? +

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

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

retrack_shipments is provided by the Trackmage MCP Server MCP server (trackmage/trackmage-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.