Look up or search UN/LOCODE — the UN Code for Trade and Transport Locations (~116k locations, all countries). Pass locode for an exact code (e.g. USNYC), or query to search names with optional country (ISO alpha-2) and function (port, rail, road, airport, postal, multimodal, fixed, border) filter...
AI agents call trade.locode to retrieve information from Mcp without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a pure data retrieval tool that queries a reference database of location codes used in shipping and trade documentation. It has no side effects, does not modify data, does not execute code or external operations, and does not involve financial transactions. The read-only nature and limited blast radius (returning only public reference data) justify low severity classification.
From the tool's definition Tool performs lookup and search operations on UN/LOCODE database: 'Look up or search UN/LOCODE', 'Pass locode for an exact code', 'query to search names'.
Attacks that exploit this kind of access
Look up or search UN/LOCODE — the UN Code for Trade and Transport Locations (~116k locations, all countries). Pass locode for an exact code (e.g. USNYC), or query to search names with optional country (ISO alpha-2) and function (port, rail, road, airport, postal, multimodal, fixed, border) filters. Returns name, subdivision, transport functions, status, IATA code, coordinates. The standard location identifier in shipping, EDI, and customs documents. It is categorised as a Read tool in the Mcp MCP Server, which means it retrieves data without modifying state.
Register the MCP server in PolicyLayer and add a rule for trade.locode: 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 Mcp. Nothing to install.
trade.locode 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 trade.locode 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 trade.locode. 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.
trade.locode is provided by the MCP server (@2sio/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →