Search 116,129 UN/LOCODE transport locations worldwide. UN/LOCODE identifies ports, airports, rail terminals, inland depots, and border crossings. Each code is 5 characters: 2-letter country code + 3-character location (e.g., GBLHR = London Heathrow, NLRTM = Rotterdam). Use this tool when you nee...
Risk signalsAccepts freeform code/query input (query)
Part of the FreightUtils MCP Server server.
Free to start. No card required.
AI agents call unlocode_lookup to retrieve information from FreightUtils MCP Server 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 unlocode_lookup 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": {
"unlocode_lookup": {}
}
}See the full FreightUtils MCP Server policy for all 19 tools.
These attack patterns abuse exactly the kind of access unlocode_lookup 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.
Search 116,129 UN/LOCODE transport locations worldwide. UN/LOCODE identifies ports, airports, rail terminals, inland depots, and border crossings. Each code is 5 characters: 2-letter country code + 3-character location (e.g., GBLHR = London Heathrow, NLRTM = Rotterdam). Use this tool when you need to: - Find a port, airport, or terminal by name - Look up a specific UN/LOCODE - Filter locations by country or function type (port, airport, rail, road, icd, border). It is categorised as a Read tool in the FreightUtils MCP Server MCP Server, which means it retrieves data without modifying state.
Register the FreightUtils MCP Server MCP server in PolicyLayer and add a rule for unlocode_lookup: 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 FreightUtils MCP Server. Nothing to install.
unlocode_lookup 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 unlocode_lookup 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 unlocode_lookup. 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.
unlocode_lookup is provided by the FreightUtils MCP Server MCP server (freightutils-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 19 FreightUtils MCP Server 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.