Get tracking checkpoints for a shipment
AI agents call get_shipment_checkpoints to retrieve information from Trackmage MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves tracking checkpoint data for an existing shipment. It is a query/fetch operation that has no side effects—it does not create, modify, delete, or execute external operations. The worst case of misuse would be unauthorized access to tracking information, a data exposure risk appropriate for the Read category at low severity.
From the tool's definition Tool name 'get_shipment_checkpoints' and description 'Get tracking checkpoints for a shipment' indicate a retrieval operation with no modification or deletion of data.
Attacks that exploit this kind of access
Get tracking checkpoints for a shipment. It is categorised as a Read tool in the Trackmage MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Trackmage MCP Server MCP server in PolicyLayer and add a rule for get_shipment_checkpoints: 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.
get_shipment_checkpoints is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_shipment_checkpoints 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.
Set action: deny in the PolicyLayer policy for get_shipment_checkpoints. 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.
get_shipment_checkpoints 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →