logistics.tracking.status
Get full tracking timeline for a registered package — latest status, all carrier scan events with timestamps and locations, delivery milestones, transit days, origin/destination countries. Supports 3,200+ carriers across 220 countries. Call tracking.register first if number is not yet registered ...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/logistics.tracking.status.md
What logistics.tracking.status does on Apibase
AI agents call logistics.tracking.status to retrieve information from Apibase without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
tracking_number | string | Yes | Tracking number previously registered with tracking.register. Returns full event timeline, carrier info, milestones, and delivery status |
Parameters from the server's own tool schema.
Why logistics.tracking.status is rated Low
Retrieves package tracking data without modifying, deleting, or executing operations. No side effects.
From the tool's definition Get full tracking timeline, latest status, carrier scan events, delivery milestones
Attacks that exploit this kind of access
The rule that runs logistics.tracking.status safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For logistics.tracking.status, this is the rule to start with:
logistics.tracking.status is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Apibase, apply this rule, and every logistics.tracking.status call is checked against it from then on.
Questions about logistics.tracking.status
Get full tracking timeline for a registered package — latest status, all carrier scan events with timestamps and locations, delivery milestones, transit days, origin/destination countries. Supports 3,200+ carriers across 220 countries. Call tracking.register first if number is not yet registered (17TRACK). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
logistics.tracking.status accepts 1 parameter: tracking_number. Required: tracking_number. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for logistics.tracking.status: 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 Apibase. Nothing to install.
logistics.tracking.status 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 logistics.tracking.status 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 logistics.tracking.status. 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.
logistics.tracking.status is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue