nominatim.geocode.search
Forward geocode a free-form address or place name (e.g. "Eiffel Tower", "1600 Amphitheatre Parkway, Mountain View") into coordinates and structured address data, using OpenStreetMap data via Nominatim. Optionally restrict to specific countries. No auth required; ODbL licensed, © OpenStreetMap con...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/nominatim.geocode.search.md
What nominatim.geocode.search does on Apibase
AI agents call nominatim.geocode.search 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 |
|---|---|---|---|
limit | integer | — | Maximum number of matches to return (1-50, default 5) |
query | string | Yes | Free-form search text (e.g. "1600 Amphitheatre Parkway, Mountain View" or "Eiffel Tower") |
language | string | — | Preferred response language as an Accept-Language value (e.g. "en", "de-DE") |
country_codes | string | — | Comma-separated ISO 3166-1 alpha-2 country codes to restrict the search to (e.g. "us,ca") |
Parameters from the server's own tool schema.
Why nominatim.geocode.search is rated Low
Tool retrieves geographic data with no side effects, modifying no underlying resources.
From the tool's definition Forward geocode address into coordinates and structured address data, no auth required.
Attacks that exploit this kind of access
The rule that runs nominatim.geocode.search 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 nominatim.geocode.search, this is the rule to start with:
nominatim.geocode.search 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 nominatim.geocode.search call is checked against it from then on.
Questions about nominatim.geocode.search
Forward geocode a free-form address or place name (e.g. "Eiffel Tower", "1600 Amphitheatre Parkway, Mountain View") into coordinates and structured address data, using OpenStreetMap data via Nominatim. Optionally restrict to specific countries. No auth required; ODbL licensed, © OpenStreetMap contributors. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
nominatim.geocode.search accepts 4 parameters: limit, query, language, country_codes. Required: query. 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 nominatim.geocode.search: 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.
nominatim.geocode.search 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 nominatim.geocode.search 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 nominatim.geocode.search. 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.
nominatim.geocode.search 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