19 critical maritime chokepoints and trade routes with oil flow (mbd), daily vessel transits, trade value share. Optional: route_type (chokepoint/canal/route), country (ISO-3).
AI agents call intel_trade_routes to retrieve information from Threat Intelligence MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
intel_trade_routes is a data retrieval tool that aggregates publicly available maritime intelligence (chokepoint locations, vessel counts, trade values). It has no side effects—it only queries and returns information. The optional parameters (route_type, country) are filter/lookup arguments, not actions that modify state or execute external operations. This fits the Read category.
From the tool's definition Tool retrieves and queries data about maritime trade routes, chokepoints, vessel transits, and oil flow statistics. Verbs used: 'with' (includes data on), implying read/retrieval.
Documented attack patterns abuse exactly the kind of access intel_trade_routes gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Threat Intelligence MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for intel_trade_routes:
{
"version": "1",
"default": "deny",
"tools": {
"intel_trade_routes": {}
}
}intel_trade_routes is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
19 critical maritime chokepoints and trade routes with oil flow (mbd), daily vessel transits, trade value share. Optional: route_type (chokepoint/canal/route), country (ISO-3). It is categorised as a Read tool in the Threat Intelligence MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Threat Intelligence MCP Server MCP server in PolicyLayer and add a rule for intel_trade_routes: 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 Threat Intelligence MCP Server. Nothing to install.
intel_trade_routes 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 intel_trade_routes 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 intel_trade_routes. 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.
intel_trade_routes is provided by the Threat Intelligence MCP Server MCP server (marc-shade/world-intel-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Threat Intelligence MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
113 Threat Intelligence MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.