geo_logistics_intel
Geospatial logistics intelligence for supply chain, maritime and transport agents. Four modes: (1) geocode_batch — resolve up to 50 addresses to lat/lon with confidence scores (OSM Nominatim + Open-Meteo fallback, 1 req/s rate-limit respected); (2) routing — road/cycling/walking route with distan...
This record as markdown: /tools/io-github-getgapup-gapup-mcp/geo-logistics-intel.md
What geo_logistics_intel does on Gapup Mcp
AI agents call geo_logistics_intel to retrieve information from Gapup Mcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
to | string | — | routing only: destination address or 'lat,lon' |
from | string | — | routing only: origin address or 'lat,lon' |
mode | string | Yes | 'geocode_batch': address -> lat/lon. 'routing': route + ETA. 'port_congestion': UN/LOCODE port state. 'ship_tracking': vessel by MMSI |
async | boolean | — | If true, returns a job_id immediately (<200ms) instead of waiting for the result. Poll the result with job_result(job_id). Use for slow tools to avoid client ti |
query | string | Yes | Primary input: address for geocode/routing, UN/LOCODE (e.g. NLRTM) for port_congestion, 9-digit MMSI for ship_tracking |
addresses | array | — | geocode_batch only: up to 50 addresses (overrides query if provided) |
mode_transport | string | — | routing only: transport mode. Default: driving |
Parameters from the server's own tool schema.
Why geo_logistics_intel is rated Low
All four described modes are data retrieval operations: geocoding addresses, computing routes, and querying port congestion status. No writes, executions, or financial transactions are performed. Severity is medium because geospatial logistics intelligence could reveal sensitive supply chain details or be misused for tracking, and the description is truncated (mode 4 is cut off), slightly lowering confidence.
From the tool's definition geocode_batch — resolve up to 50 addresses to lat/lon; routing — road/cycling/walking route with distance_km, duration_seconds and ETA; port_congestion — congestion status for any UN/LOCODE port with waiting vessel count, severity and average wait hours
Risk signalsAccepts freeform code/query input (query)
Attacks that exploit this kind of access
The rule that runs geo_logistics_intel safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Gapup Mcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For geo_logistics_intel, this is the rule to start with:
geo_logistics_intel is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Gapup Mcp, apply this rule, and every geo_logistics_intel call is checked against it from then on.
Questions about geo_logistics_intel
Geospatial logistics intelligence for supply chain, maritime and transport agents. Four modes: (1) geocode_batch — resolve up to 50 addresses to lat/lon with confidence scores (OSM Nominatim + Open-Meteo fallback, 1 req/s rate-limit respected); (2) routing — road/cycling/walking route with distance_km, duration_seconds and ETA ISO timestamp between two addresses or lat/lon points (OSRM public, keyless, global); (3) port_congestion — congestion status for any UN/LOCODE port (e.g. NLRTM, SGSIN, CNSHA) with waiting vessel count, severity (low/medium/high/extreme) and average wait hours; (4) ship_tracking — AIS position, speed, course, destination and ETA for a vessel by its 9-digit MMSI. No API key required for geocode/routing/port. Optional env: AIS_STREAM_API_KEY for live ship data (otherwise MarineTraffic scrape best-effort). SLA: <=25s p95. Cache: 24h geocoding / 1h routing / 30min port / 5min ship. Quality score 0-100. Status: final/partial/failed. It is categorised as a Read tool in the Gapup Mcp MCP Server, which means it retrieves data without modifying state.
geo_logistics_intel accepts 7 parameters: to, from, mode, async, query, addresses, mode_transport. Required: mode, query. The full parameter table on this page comes from the server's own tool schema.
Register the Gapup MCP server in PolicyLayer and add a rule for geo_logistics_intel: 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 Gapup Mcp. Nothing to install.
geo_logistics_intel 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 geo_logistics_intel 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 geo_logistics_intel. 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.
geo_logistics_intel is provided by the Gapup MCP server (https://mcp.gapup.io/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Gapup, and thousands of servers like it.
This server
Across the catalogue