get_cargo_tariff
Get live cargo tariff; args: origin/destination aliases, lang/language en|lt|pl|de.
This record as markdown: /tools/com-fromtocargo-mcp/get-cargo-tariff.md
What get_cargo_tariff does on Mcp
AI agents call get_cargo_tariff 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 |
|---|---|---|---|
to | string | — | |
lang | string | — | |
from_ | string | — | |
origin | string | — | |
pickup | string | — | |
source | string | — | |
target | string | — | |
to_city | string | — | |
delivery | string | — | |
language | string | — | |
from_city | string | — | |
destination | string | — |
Parameters from the server's own tool schema.
Why get_cargo_tariff is rated Low
Even though get_cargo_tariff 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 (12 properties)
Attacks that exploit this kind of access
The rule that runs get_cargo_tariff 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 get_cargo_tariff, this is the rule to start with:
get_cargo_tariff 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 get_cargo_tariff call is checked against it from then on.
Questions about get_cargo_tariff
Get live cargo tariff; args: origin/destination aliases, 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.
get_cargo_tariff accepts 12 parameters: to, lang, from_, origin, pickup, source, target, to_city, delivery, language, from_city, destination. 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 get_cargo_tariff: 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.
get_cargo_tariff 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_cargo_tariff 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_cargo_tariff. 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_cargo_tariff 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