Monitor risk levels across 10 major ocean freight trade corridors (China-US West Coast, China-US East Coast, China-Mexico, Taiwan-US, India-US, China-Europe, Europe-US, Middle East-Europe, Brazil-US). Each corridor chains origin ports, chokepoints, and destination ports into a single lane scored ...
Part of the Supply Chain Intelligence server.
Free to start. No card required.
AI agents call get_corridor_risk to retrieve information from Supply Chain Intelligence without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though get_corridor_risk only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"get_corridor_risk": {}
}
}See the full Supply Chain Intelligence policy for all 31 tools.
These attack patterns abuse exactly the kind of access get_corridor_risk gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Monitor risk levels across 10 major ocean freight trade corridors (China-US West Coast, China-US East Coast, China-Mexico, Taiwan-US, India-US, China-Europe, Europe-US, Middle East-Europe, Brazil-US). Each corridor chains origin ports, chokepoints, and destination ports into a single lane scored by its weakest link (highest risk waypoint). Scores combine real-time port congestion data with active natural disaster proximity. Used by logistics planners for route risk comparison, procurement teams for supply chain exposure assessment, and freight forwarders for disruption early warning.. It is categorised as a Read tool in the Supply Chain Intelligence MCP Server, which means it retrieves data without modifying state.
Register the Supply Chain Intelligence MCP server in PolicyLayer and add a rule for get_corridor_risk: 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 Supply Chain Intelligence. Nothing to install.
get_corridor_risk 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_corridor_risk 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_corridor_risk. 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_corridor_risk is provided by the Supply Chain Intelligence MCP server (https://supplymaven.com/api/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 31 Supply Chain Intelligence tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.