indec-georef.admin.localities
Search Argentine localities (cities/towns) by name, optionally scoped to a province. Returns id, name, category, parent province/department/municipality, and centroid coordinates. Data: apis.datos.gob.ar/georef (INDEC), no auth required.
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/indec-georef.admin.localities.md
What indec-georef.admin.localities does on Apibase
AI agents call indec-georef.admin.localities 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 localities to return (1-50, default 10). |
query | string | Yes | Locality (city/town) name to search for, case-insensitive (e.g. "Palermo"). |
provincia | string | — | Restrict results to a province, by name or id (e.g. "Santa Fe" or "82"). |
Parameters from the server's own tool schema.
Why indec-georef.admin.localities is rated Low
Retrieves geographic reference data with no side effects or sensitive operations.
From the tool's definition Search Argentine localities by name. Returns id, name, category, coordinates. No auth required.
Attacks that exploit this kind of access
The rule that runs indec-georef.admin.localities 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.admin.localities, this is the rule to start with:
indec-georef.admin.localities 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.admin.localities call is checked against it from then on.
Questions about indec-georef.admin.localities
Search Argentine localities (cities/towns) by name, optionally scoped to a province. Returns id, name, category, parent province/department/municipality, and centroid coordinates. 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.admin.localities accepts 3 parameters: max, query, provincia. 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 indec-georef.admin.localities: 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.admin.localities 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.admin.localities 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.admin.localities. 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.admin.localities 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