Query 40+ strategic ports worldwide: container mega-ports, oil/LNG terminals, naval bases, bulk ports. Filterable by type and country.
AI agents call intel_strategic_ports 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.
This tool retrieves information about strategic port locations, capacities, and characteristics. While categorized as Read (data retrieval with no side effects), the severity is elevated to 'medium' rather than 'low' because the information aggregated—port locations, types, and global infrastructure details—could be misused for planning physical attacks, supply chain disruption, or geopolitical intelligence…
From the tool's definition Tool name includes 'Query' and description states 'Query 40+ strategic ports' — the core function is data retrieval with no modification or destructive capability.
Documented attack patterns abuse exactly the kind of access intel_strategic_ports 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_strategic_ports:
{
"version": "1",
"default": "deny",
"tools": {
"intel_strategic_ports": {}
}
}intel_strategic_ports 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.
Query 40+ strategic ports worldwide: container mega-ports, oil/LNG terminals, naval bases, bulk ports. Filterable by type and country. 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_strategic_ports: 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_strategic_ports 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_strategic_ports 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_strategic_ports. 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_strategic_ports 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.