indec-georef.location.reverse_geocode
Reverse geocode a lat/lon coordinate pair within Argentina to its administrative location — province, department, and municipality. Data: apis.datos.gob.ar/georef (INDEC), no auth required.
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/indec-georef.location.reverse-geocode.md
What indec-georef.location.reverse_geocode does on Apibase
AI agents call indec-georef.location.reverse_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 |
|---|---|---|---|
lat | number | Yes | Latitude in decimal degrees (e.g. -34.6). |
lon | number | Yes | Longitude in decimal degrees (e.g. -58.45). |
Parameters from the server's own tool schema.
Why indec-georef.location.reverse_geocode is rated Low
Retrieves geographic location data from public government API; no side effects or modifications.
From the tool's definition Reverse geocode a lat/lon coordinate pair...to its administrative location
Risk signalsAdmin/system-level operation
Attacks that exploit this kind of access
The rule that runs indec-georef.location.reverse_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 indec-georef.location.reverse_geocode, this is the rule to start with:
indec-georef.location.reverse_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 indec-georef.location.reverse_geocode call is checked against it from then on.
Questions about indec-georef.location.reverse_geocode
Reverse geocode a lat/lon coordinate pair within Argentina to its administrative location — province, department, and municipality. Data: apis.datos.gob.ar/georef (INDEC), no auth required. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
indec-georef.location.reverse_geocode accepts 2 parameters: lat, lon. Required: lat, lon. 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 indec-georef.location.reverse_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.
indec-georef.location.reverse_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 indec-georef.location.reverse_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 indec-georef.location.reverse_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.
indec-georef.location.reverse_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