Return waiting packages from the local package cache.
AI agents call get_my_packages 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.
This tool retrieves package tracking information from a local cache without creating, modifying, deleting, executing code, or initiating financial transactions. It is a straightforward query operation that returns existing data to the user. The blast radius of misuse is minimal—an agent would only be able to view package information already cached locally, not modify it or trigger external actions.
From the tool's definition Tool name 'get_my_packages' and description 'Return waiting packages from the local package cache' indicate data retrieval with no side effects or modifications.
Attacks that exploit this kind of access
Return waiting packages 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 get_my_packages: 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.
get_my_packages 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 get_my_packages 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 get_my_packages. 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.
get_my_packages 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 →