Resolve a postal/ZIP code to place name(s), administrative divisions (state/province, county/district), and coordinates. Pass postalCode + 2-letter country (default US). International — major markets (US, GB, CA, DE, FR, AU, NL, ES, IT, CH, SE, MX). Normalize + enrich addresses or derive state/co...
AI agents call geo.postal 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 tool retrieves geographical and administrative information in response to postal code queries. It has no side effects, does not create or modify data, does not execute arbitrary code or shell commands, and does not perform financial transactions. The 'enrich addresses' function is informational enrichment only.
From the tool's definition Tool description states it 'Resolve[s]' and 'Normalize[s]' postal codes to place names and coordinates—purely a lookup and data retrieval operation with no modification, deletion, or execution of external commands.
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
Resolve a postal/ZIP code to place name(s), administrative divisions (state/province, county/district), and coordinates. Pass postalCode + 2-letter country (default US). International — major markets (US, GB, CA, DE, FR, AU, NL, ES, IT, CH, SE, MX). Normalize + enrich addresses or derive state/county for a ZIP. 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 geo.postal: 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.
geo.postal 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.postal 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.postal. 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.postal 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 →