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...
Part of the Livedatalink server.
Free to start. No card required.
AI agents call package_track to retrieve information from Livedatalink without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though package_track only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"package_track": {}
}
}See the full Livedatalink policy for all 177 tools.
These attack patterns abuse exactly the kind of access package_track gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
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.
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.
Deterministic rules across all 177 Livedatalink tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.