logistics.dhl.track
Track a DHL shipment by tracking number — returns current status, delivery events timeline, origin/destination, estimated delivery date, and service type. Supports all DHL services: Express, Parcel, eCommerce, Freight. Official DHL data for 220+ countries (DHL)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/logistics.dhl.track.md
What logistics.dhl.track does on Apibase
AI agents call logistics.dhl.track to retrieve information from Apibase 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 | DHL tracking number (e.g. "00340434292135100186" for DHL Paket, "1234567890" for DHL Express). Supports all DHL services: Express, Parcel, eCommerce, Freight |
Parameters from the server's own tool schema.
Why logistics.dhl.track is rated Low
Tool retrieves shipment tracking data with no side effects or modifications.
From the tool's definition Track a DHL shipment by tracking number — returns current status, delivery events timeline
Attacks that exploit this kind of access
The rule that runs logistics.dhl.track safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For logistics.dhl.track, this is the rule to start with:
logistics.dhl.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 Apibase, apply this rule, and every logistics.dhl.track call is checked against it from then on.
Questions about logistics.dhl.track
Track a DHL shipment by tracking number — returns current status, delivery events timeline, origin/destination, estimated delivery date, and service type. Supports all DHL services: Express, Parcel, eCommerce, Freight. Official DHL data for 220+ countries (DHL). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
logistics.dhl.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 Apibase MCP server in PolicyLayer and add a rule for logistics.dhl.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 Apibase. Nothing to install.
logistics.dhl.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 logistics.dhl.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 logistics.dhl.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.
logistics.dhl.track is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue