gov.ibge.name_frequency
First-name popularity time-series by decade since 1930 from Brazilian census data — useful for cultural/marketing research. IBGE CC BY 4.0
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/gov.ibge.name-frequency.md
What gov.ibge.name_frequency does on Apibase
AI agents call gov.ibge.name_frequency 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 |
|---|---|---|---|
name | string | Yes | First name (e.g. "MARIA", "JOSE"). Returns name frequency time-series by decade since 1930 from Brazilian census data. |
Parameters from the server's own tool schema.
Why gov.ibge.name_frequency is rated Low
Retrieves historical demographic statistics from public census data with no modification or side effects.
From the tool's definition First-name popularity time-series; Brazilian census data; cultural/marketing research
Attacks that exploit this kind of access
The rule that runs gov.ibge.name_frequency 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.name_frequency, this is the rule to start with:
gov.ibge.name_frequency 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.name_frequency call is checked against it from then on.
Questions about gov.ibge.name_frequency
First-name popularity time-series by decade since 1930 from Brazilian census data — useful for cultural/marketing research. 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.name_frequency accepts 1 parameter: name. Required: name. 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.name_frequency: 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.name_frequency 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.name_frequency 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.name_frequency. 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.name_frequency 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