estimate_cargo_price
Estimate cargo price; args: origin/destination aliases; volume_m3/m3/cbm/volume, weight_kg/kg/weight, pallets/pll/epal/pallet_count, ldm/loading_meters/lademeter; lang/language en|lt|pl|de.
This record as markdown: /tools/com-fromtocargo-mcp/estimate-cargo-price.md
What estimate_cargo_price does on Mcp
AI agents call estimate_cargo_price to retrieve information from Mcp 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 |
|---|---|---|---|
kg | number | — | |
m3 | number | — | |
to | string | — | |
cbm | number | — | |
ldm | number | — | |
pll | number | — | |
epal | number | — | |
lang | string | — | |
from_ | string | — | |
origin | string | — | |
pickup | string | — | |
source | string | — |
Parameters from the server's own tool schema.
Why estimate_cargo_price is rated Low
Even though estimate_cargo_price only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Risk signalsAccepts file system path (destination) · High parameter count (26 properties)
Attacks that exploit this kind of access
The rule that runs estimate_cargo_price safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For estimate_cargo_price, this is the rule to start with:
estimate_cargo_price 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 Mcp, apply this rule, and every estimate_cargo_price call is checked against it from then on.
Questions about estimate_cargo_price
Estimate cargo price; args: origin/destination aliases; volume_m3/m3/cbm/volume, weight_kg/kg/weight, pallets/pll/epal/pallet_count, ldm/loading_meters/lademeter; lang/language en|lt|pl|de. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.
estimate_cargo_price accepts 12 parameters: kg, m3, to, cbm, ldm, pll, epal, lang, from_, origin, pickup, source. The full parameter table on this page comes from the server's own tool schema.
Register the MCP server in PolicyLayer and add a rule for estimate_cargo_price: 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 Mcp. Nothing to install.
estimate_cargo_price 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 estimate_cargo_price 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 estimate_cargo_price. 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.
estimate_cargo_price is provided by the MCP server (https://mcp.fromtocargo.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on , and thousands of servers like it.
This server
Across the catalogue