logistics.shipengine.rates
Compare shipping rates across multiple carriers (USPS, UPS, FedEx, DHL) for a package. Provide origin/destination ZIP codes, weight in pounds, and optional dimensions. Returns sorted rates with price, delivery time, and service type. Up to 84% off retail rates (ShipEngine)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/logistics.shipengine.rates.md
What logistics.shipengine.rates does on Apibase
AI agents call logistics.shipengine.rates 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 |
|---|---|---|---|
width | number | — | Package width in inches |
height | number | — | Package height in inches |
length | number | — | Package length in inches |
to_zip | string | Yes | Destination US ZIP code (e.g. "90210" for Beverly Hills) |
from_zip | string | Yes | Origin US ZIP code (e.g. "10001" for NYC) |
weight_lb | number | Yes | Package weight in pounds (e.g. 5) |
to_country | string | — | Destination country code (default US) |
from_country | string | — | Origin country code (default US) |
Parameters from the server's own tool schema.
Why logistics.shipengine.rates is rated Low
Tool queries shipping rates without modifying data or triggering transactions. Read-only information retrieval.
From the tool's definition Compare shipping rates across multiple carriers. Returns sorted rates with price, delivery time.
Attacks that exploit this kind of access
The rule that runs logistics.shipengine.rates 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.shipengine.rates, this is the rule to start with:
logistics.shipengine.rates 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.shipengine.rates call is checked against it from then on.
Questions about logistics.shipengine.rates
Compare shipping rates across multiple carriers (USPS, UPS, FedEx, DHL) for a package. Provide origin/destination ZIP codes, weight in pounds, and optional dimensions. Returns sorted rates with price, delivery time, and service type. Up to 84% off retail rates (ShipEngine). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
logistics.shipengine.rates accepts 8 parameters: width, height, length, to_zip, from_zip, weight_lb, to_country, from_country. Required: to_zip, from_zip, weight_lb. 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.shipengine.rates: 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.shipengine.rates 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.shipengine.rates 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.shipengine.rates. 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.shipengine.rates 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