gov.ibge.municipalities
List all 5,570 Brazilian municipalities (or filtered by 2-letter state code) with IBGE codes. IBGE CC BY 4.0
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/gov.ibge.municipalities.md
What gov.ibge.municipalities does on Apibase
AI agents call gov.ibge.municipalities 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 |
|---|---|---|---|
uf | string | — | Optional 2-letter Brazilian state code (e.g. "SP" for São Paulo, "RJ" for Rio de Janeiro). If omitted, returns all 5,570 municipalities. |
limit | integer | — | Max municipalities to return (default 200, max 2000 — useful for pagination). |
Parameters from the server's own tool schema.
Why gov.ibge.municipalities is rated Low
Retrieves public municipality data without modification or side effects.
From the tool's definition List all Brazilian municipalities with IBGE codes
Attacks that exploit this kind of access
The rule that runs gov.ibge.municipalities 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 gov.ibge.municipalities, this is the rule to start with:
gov.ibge.municipalities 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 gov.ibge.municipalities call is checked against it from then on.
Questions about gov.ibge.municipalities
List all 5,570 Brazilian municipalities (or filtered by 2-letter state code) with IBGE codes. IBGE CC BY 4.0. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
gov.ibge.municipalities accepts 2 parameters: uf, limit. 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 gov.ibge.municipalities: 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.
gov.ibge.municipalities 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 gov.ibge.municipalities 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 gov.ibge.municipalities. 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.
gov.ibge.municipalities 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