geo.address.geocode
Convert an address, place name, or landmark to geographic coordinates (lat/lon) with structured address data (Geoapify/OSM)
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/geo.address.geocode.md
What geo.address.geocode does on Apibase
AI agents call geo.address.geocode 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 |
|---|---|---|---|
lang | string | — | Result language code (e.g. "en", "de", "ru"). Default: English. |
text | string | Yes | Address, place name, or landmark to geocode (e.g. "1600 Pennsylvania Ave, Washington DC", "Eiffel Tower"). |
type | string | — | Filter by result type: city, street, amenity, or country. |
limit | integer | — | Maximum number of results to return (default 1, max 5). |
country_code | string | — | ISO 3166-1 alpha-2 country code to filter results (e.g. "US", "DE", "FR"). |
Parameters from the server's own tool schema.
Why geo.address.geocode is rated Low
Geocoding is a query operation that retrieves geographic data without side effects or data modification.
From the tool's definition Convert an address to geographic coordinates; retrieves structured address data.
Attacks that exploit this kind of access
The rule that runs geo.address.geocode 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 geo.address.geocode, this is the rule to start with:
geo.address.geocode 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 geo.address.geocode call is checked against it from then on.
Questions about geo.address.geocode
Convert an address, place name, or landmark to geographic coordinates (lat/lon) with structured address data (Geoapify/OSM). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
geo.address.geocode accepts 5 parameters: lang, text, type, limit, country_code. Required: text. 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 geo.address.geocode: 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.
geo.address.geocode 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.address.geocode 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.address.geocode. 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.address.geocode 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