Get global shipping and freight rates: Baltic Dry Index (BDI) for bulk shipping, Freightos container spot rates for major routes, port congestion indices, and supply chain stress signals. Use this tool when: - A macro agent wants shipping rates as a leading indicator of global trade volumes - A s...
AI agents call get_shipping_rates to retrieve information from Omni Service Node without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries market data sources (BDI indices, Freightos rates, port congestion data) and returns information for analysis. It performs no state changes, has no side effects, and merely retrieves publicly available or subscription-based market signals.
From the tool's definition Tool retrieves and returns shipping rate data: 'Get global shipping and freight rates: Baltic Dry Index (BDI) for bulk shipping, Freightos container spot rates for major routes, port congestion indices, and supply chain stress signals.' Returns include…
Attacks that exploit this kind of access
Get global shipping and freight rates: Baltic Dry Index (BDI) for bulk shipping, Freightos container spot rates for major routes, port congestion indices, and supply chain stress signals. Use this tool when: - A macro agent wants shipping rates as a leading indicator of global trade volumes - A supply chain risk agent is monitoring for port congestion or freight disruptions - You need to assess inflation pressures from elevated freight costs - An agent is monitoring the impact of geopolitical events (Red Sea, Panama Canal) on shipping routes Returns: baltic_dry_index, BDI_change_pct, container_rates (per route, per 40ft container), port_congestion_indices, supply_chain_stress_score, key_disruptions. Example: getShippingRates({ routes:. It is categorised as a Read tool in the Omni Service Node MCP Server, which means it retrieves data without modifying state.
Register the Omni Service Node MCP server in PolicyLayer and add a rule for get_shipping_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 Omni Service Node. Nothing to install.
get_shipping_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 get_shipping_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 get_shipping_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.
get_shipping_rates is provided by the Omni Service Node MCP server (luckkyyy23/omni-service-node). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →