address.postal.lookup
Look up a postal/ZIP code in 60+ countries — returns city name, state/region, and lat/lon coordinates. Supports US, UK, Germany, France, Japan, Brazil, India, Australia, and 50+ more countries. Provide country code (ISO 2-letter) + postal code (Zippopotam.us)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/address.postal.lookup.md
What address.postal.lookup does on Apibase
AI agents call address.postal.lookup to retrieve information from Apibase 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 |
|---|---|---|---|
postal_code | string | Yes | Postal/ZIP code (e.g. "90210" for US, "10115" for Germany, "SW1A" for UK, "75001" for France) |
country_code | string | Yes | ISO 3166-1 alpha-2 country code (e.g. "us", "de", "gb", "fr", "jp", "br", "in", "au"). Supports 60+ countries |
Parameters from the server's own tool schema.
Why address.postal.lookup is rated Low
Tool retrieves public geographic data with no state modification, deletion, or financial impact.
From the tool's definition Look up a postal/ZIP code — returns city name, state/region, lat/lon coordinates
Attacks that exploit this kind of access
The rule that runs address.postal.lookup safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For address.postal.lookup, this is the rule to start with:
address.postal.lookup 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 Apibase, apply this rule, and every address.postal.lookup call is checked against it from then on.
Questions about address.postal.lookup
Look up a postal/ZIP code in 60+ countries — returns city name, state/region, and lat/lon coordinates. Supports US, UK, Germany, France, Japan, Brazil, India, Australia, and 50+ more countries. Provide country code (ISO 2-letter) + postal code (Zippopotam.us). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
address.postal.lookup accepts 2 parameters: postal_code, country_code. Required: postal_code, country_code. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for address.postal.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 Apibase. Nothing to install.
address.postal.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 address.postal.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 address.postal.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.
address.postal.lookup is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue