package_track
Track a package or shipment by tracking number. Auto-detects carrier (USPS, UPS, FedEx, DHL, Amazon). Returns delivery status, current location, estimated delivery date, and tracking history. Use this for 'where is my package?', 'track this shipment', 'when will my order arrive?', 'check delivery...
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/package-track.md
What package_track does on Livedatalink
AI agents call package_track to retrieve information from Livedatalink 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 | Package tracking number from any carrier |
Parameters from the server's own tool schema.
Why package_track is rated Low
package_track retrieves and queries package delivery information without creating, modifying, or deleting any data. It has no side effects on the tracked shipment or any system. This is a straightforward read operation, classified as Read category with low severity due to minimal blast radius if misused (an agent could only retrieve publicly available tracking information).
From the tool's definition Tool 'returns delivery status, current location, estimated delivery date, and tracking history' — purely informational queries with no modification of data or side effects. The description uses read-only language: 'track', 'returns', 'check'.
Attacks that exploit this kind of access
The rule that runs package_track safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Livedatalink, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For package_track, this is the rule to start with:
package_track 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 Livedatalink, apply this rule, and every package_track call is checked against it from then on.
Questions about package_track
Track a package or shipment by tracking number. Auto-detects carrier (USPS, UPS, FedEx, DHL, Amazon). Returns delivery status, current location, estimated delivery date, and tracking history. Use this for 'where is my package?', 'track this shipment', 'when will my order arrive?', 'check delivery status', 'is my package delivered?', or any package tracking question. Just paste the tracking number - the carrier is detected automatically. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
package_track 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 Livedatalink MCP server in PolicyLayer and add a rule for package_track: 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 Livedatalink. Nothing to install.
package_track 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 package_track 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 package_track. 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.
package_track is provided by the Livedatalink MCP server (https://livedatalink.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Livedatalink, and thousands of servers like it.
This server
Across the catalogue