sendle_track_parcel
Track a Sendle parcel by tracking number.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/sendle-track-parcel.md
What sendle_track_parcel does on UnClick
AI agents call sendle_track_parcel to retrieve information from UnClick 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 |
|---|---|---|---|
api_key | string | — | |
tracking_id | string | Yes |
Parameters from the server's own tool schema.
Why sendle_track_parcel is rated Low
This tool queries parcel tracking data using a tracking number and returns status information. It is a read-only operation with no side effects, no data modification, and no external state changes. The blast radius of misuse is minimal—an agent could retrieve parcel information for tracking numbers it doesn't own, but this represents a minor information disclosure risk typical of Read operations.
From the tool's definition Tool name 'sendle_track_parcel' and description 'Track a Sendle parcel by tracking number' indicate a query operation that retrieves shipping/parcel status information without modifying data.
Risk signalsHandles credentials or secrets (api_key)
Attacks that exploit this kind of access
The rule that runs sendle_track_parcel safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For sendle_track_parcel, this is the rule to start with:
sendle_track_parcel 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 UnClick, apply this rule, and every sendle_track_parcel call is checked against it from then on.
Questions about sendle_track_parcel
Track a Sendle parcel by tracking number. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
sendle_track_parcel accepts 2 parameters: api_key, tracking_id. Required: tracking_id. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for sendle_track_parcel: 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 UnClick. Nothing to install.
sendle_track_parcel 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 sendle_track_parcel 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 sendle_track_parcel. 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.
sendle_track_parcel is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue