update_shipment · Trackmage MCP Server MCP: Risk & Policy

WHAT IT DOES

What update_shipment does on Trackmage MCP Server

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

WHY IT NEEDS A POLICY

Why update_shipment needs a policy

The tool modifies existing shipment records (reversible operation), which constitutes a Write action. Severity is medium because erroneous updates to shipments could disrupt logistics workflows and cause operational issues, but changes are typically reversible through subsequent corrections. Confidence is high based on clear naming and API context.

From the tool's definition Tool name 'update_shipment' and description 'Update an existing shipment' indicate modification of shipment data.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_shipment Rate-limited

update_shipment 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": {
    "update_shipment": {
      "limits": [
        {
          "counter": "update_shipment_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 Trackmage MCP Server, so you can run agents against it safely.

FAQ

Questions about update_shipment

What does the update_shipment tool do? +

Update an existing shipment. It is categorised as a Write tool in the Trackmage 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 update_shipment? +

Register the Trackmage MCP Server MCP server in PolicyLayer and add a rule for update_shipment: 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 update_shipment? +

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

Can I rate-limit update_shipment? +

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

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

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