Monitor real-time port congestion and vessel traffic at 26 major global ports. Returns vessel counts at berth and at anchor, congestion score versus historical baseline, and port status. Covers US ports (Los Angeles, Long Beach, Savannah, Houston, New York/New Jersey, Charleston, Oakland, Seattle...
Part of the Risk Intelligence server.
Free to start. No card required.
AI agents call port_congestion_monitor to retrieve information from Risk 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 port_congestion_monitor 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": {
"port_congestion_monitor": {}
}
}See the full Risk Intelligence policy for all 31 tools.
These attack patterns abuse exactly the kind of access port_congestion_monitor 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 real-time port congestion and vessel traffic at 26 major global ports. Returns vessel counts at berth and at anchor, congestion score versus historical baseline, and port status. Covers US ports (Los Angeles, Long Beach, Savannah, Houston, New York/New Jersey, Charleston, Oakland, Seattle, Tacoma), Asian ports (Shanghai, Singapore, Busan, Ningbo, Shenzhen, Hong Kong), and European ports (Rotterdam, Hamburg, Antwerp, Felixstowe, Piraeus). Used by freight forwarders, logistics teams, and importers to monitor delays, plan routing, and anticipate lead time changes.. It is categorised as a Read tool in the Risk Intelligence MCP Server, which means it retrieves data without modifying state.
Register the Risk Intelligence MCP server in PolicyLayer and add a rule for port_congestion_monitor: 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 Risk Intelligence. Nothing to install.
port_congestion_monitor 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 port_congestion_monitor 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 port_congestion_monitor. 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.
port_congestion_monitor is provided by the Risk Intelligence MCP server (https://www.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 Risk 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.