Return one package by package ID or tracking number from the local package cache.
AI agents call track_package to retrieve information from Parcel Pilot MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool only retrieves a single package record from a local cache based on an identifier. It has no side effects, does not modify data, and does not interact with external services at query time. Severity is low because it only exposes personal shipment tracking data for a single package.
From the tool's definition Return one package by package ID or tracking number from the local package cache.
Attacks that exploit this kind of access
Return one package by package ID or tracking number from the local package cache. It is categorised as a Read tool in the Parcel Pilot MCP MCP Server, which means it retrieves data without modifying state.
Register the Parcel Pilot MCP server in PolicyLayer and add a rule for track_package: 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 Parcel Pilot MCP. Nothing to install.
track_package 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 track_package 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 track_package. 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.
track_package is provided by the Parcel Pilot MCP server (jieyangxchen/parcel-pilot-mcp). 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 →