New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

geonames.postal.lookup

Look up postal / ZIP codes and their place names across 100+ countries using the GeoNames database. Search by postal code (e.g. "10001" for NYC, "SW1A 1AA" for London, "75001" for Paris) or by place name. Returns matching postal codes with lat/lng, admin area names, and ISO-3166-2 subdivision cod...

SERVERApibase SOURCEapibase-mcp-client
Low RISK CLASS
Category Read
Parameters 40 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-whiteknightonhorse-apibase/geonames.postal.lookup.md

What geonames.postal.lookup does on Apibase

AI agents call geonames.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.

ParameterTypeRequiredDescription
country string — ISO-3166 2-letter country code to restrict the postal code search (e.g. "US", "GB", "DE")
max_rows integer — Maximum number of results to return (default 10, max 1000)
place_name string — Place or city name to search postal codes for (e.g. "Berlin", "Sydney"). Use with country for best results.
postal_code string — Postal / ZIP code to look up (e.g. "10001" for New York, "SW1A 1AA" for London)

Parameters from the server's own tool schema.

Why geonames.postal.lookup is rated Low

Tool retrieves postal code and geographic data from a public database with no side effects or modification capability.

From the tool's definition Look up postal codes, search by postal code or place name, returns matching postal codes with data.

Risk signalsAdmin/system-level operation

Questions about geonames.postal.lookup

What does the geonames.postal.lookup tool do? +

Look up postal / ZIP codes and their place names across 100+ countries using the GeoNames database. Search by postal code (e.g. "10001" for NYC, "SW1A 1AA" for London, "75001" for Paris) or by place name. Returns matching postal codes with lat/lng, admin area names, and ISO-3166-2 subdivision codes. Use the country filter (ISO-3166 2-letter) to narrow results. Covers US, UK, Germany, France, Australia, Canada, Japan, India, Brazil, and 90+ more. CC BY 4.0 open data, no upstream cost. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.

What parameters does geonames.postal.lookup accept? +

geonames.postal.lookup accepts 4 parameters: country, max_rows, place_name, postal_code. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on geonames.postal.lookup? +

Register the Apibase MCP server in PolicyLayer and add a rule for geonames.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.

What risk level is geonames.postal.lookup? +

geonames.postal.lookup is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit geonames.postal.lookup? +

Yes. Add a rate_limit block to the geonames.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.

How do I block geonames.postal.lookup completely? +

Set action: deny in the PolicyLayer policy for geonames.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.

What MCP server provides geonames.postal.lookup? +

geonames.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.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Apibase's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.