logistics.tracking.register
⚡ ACTION: Register a tracking number to begin monitoring shipment status. Auto-detects carrier from 3,200+ supported carriers worldwide (UPS, FedEx, DHL, USPS, China Post, Royal Mail, etc.). Must be called before tracking.status. Returns detected carrier and registration status. Consumes quota — ...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/logistics.tracking.register.md
What logistics.tracking.register does on Apibase
AI agents call logistics.tracking.register 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 |
|---|---|---|---|
tag | string | — | Optional label for this shipment (e.g. order ID, customer reference). Up to 50 characters |
tracking_number | string | Yes | Package tracking number (e.g. "1Z999AA10123456784" for UPS, "9400111899560243888780" for USPS). Carrier is auto-detected from 3,200+ supported carriers |
Parameters from the server's own tool schema.
Why logistics.tracking.register is rated Low
Even though logistics.tracking.register only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs logistics.tracking.register 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.register, this is the rule to start with:
logistics.tracking.register 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.register call is checked against it from then on.
Questions about logistics.tracking.register
⚡ ACTION: Register a tracking number to begin monitoring shipment status. Auto-detects carrier from 3,200+ supported carriers worldwide (UPS, FedEx, DHL, USPS, China Post, Royal Mail, etc.). Must be called before tracking.status. Returns detected carrier and registration status. Consumes quota — 200 free/month (17TRACK). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
logistics.tracking.register accepts 2 parameters: tag, 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.register: 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.register 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.register 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.register. 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.register 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