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

geo.address.reverse

Convert geographic coordinates (lat/lon) to a structured address — street, city, country, postal code (Geoapify/OSM)

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

This record as markdown: /tools/io-github-whiteknightonhorse-apibase/geo.address.reverse.md

What geo.address.reverse does on Apibase

AI agents call geo.address.reverse 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
lat number Yes Latitude of the point to reverse geocode.
lon number Yes Longitude of the point to reverse geocode.
lang string — Result language code (e.g. "en", "de", "ru"). Default: English.

Parameters from the server's own tool schema.

Why geo.address.reverse is rated Low

Tool queries geolocation data and returns address information with no side effects.

From the tool's definition Convert geographic coordinates to structured address; retrieves location data.

Questions about geo.address.reverse

What does the geo.address.reverse tool do? +

Convert geographic coordinates (lat/lon) to a structured address — street, city, country, postal code (Geoapify/OSM). It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.

What parameters does geo.address.reverse accept? +

geo.address.reverse accepts 3 parameters: lat, lon, lang. Required: lat, lon. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on geo.address.reverse? +

Register the Apibase MCP server in PolicyLayer and add a rule for geo.address.reverse: 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 geo.address.reverse? +

geo.address.reverse is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit geo.address.reverse? +

Yes. Add a rate_limit block to the geo.address.reverse 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 geo.address.reverse completely? +

Set action: deny in the PolicyLayer policy for geo.address.reverse. 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 geo.address.reverse? +

geo.address.reverse 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.