indec-georef.location.geocode
Forward geocode an Argentine street address (e.g. "Av Corrientes 1000") to matching locations with lat/lon coordinates, street name/number, province, department, and locality. Returns multiple candidates when the address matches more than one place nationwide. Data: apis.datos.gob.ar/georef (INDE...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/indec-georef.location.geocode.md
What indec-georef.location.geocode does on Apibase
AI agents call indec-georef.location.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 |
|---|---|---|---|
max | integer | — | Maximum number of address matches to return (1-50, default 10). |
address | string | Yes | Argentine street address to geocode, street name + house number (e.g. "Av Corrientes 1000"). Returns matching addresses with lat/lon and administrative location |
Parameters from the server's own tool schema.
Why indec-georef.location.geocode is rated Low
Tool queries geographic data and returns location information without modifying or executing anything.
From the tool's definition Forward geocode an Argentine street address to matching locations with lat/lon coordinates.
Attacks that exploit this kind of access
The rule that runs indec-georef.location.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.geocode, this is the rule to start with:
indec-georef.location.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.geocode call is checked against it from then on.
Questions about indec-georef.location.geocode
Forward geocode an Argentine street address (e.g. "Av Corrientes 1000") to matching locations with lat/lon coordinates, street name/number, province, department, and locality. Returns multiple candidates when the address matches more than one place nationwide. Data: apis.datos.gob.ar/georef (INDEC — Instituto Nacional de Estadística y Censos), 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.geocode accepts 2 parameters: max, address. Required: address. 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.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.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.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.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.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