census.data.population
Get population counts for any US geography by FIPS code — total, male, female. Covers all 50 states, 3,000+ counties, and sub-county areas. Source: American Community Survey 5-year estimates (US Census Bureau). Public domain, updated annually.
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/census.data.population.md
What census.data.population does on Apibase
AI agents call census.data.population 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 |
|---|---|---|---|
year | integer | — | Survey year (default 2022). ACS 5-year estimates available 2010-2022. |
state_fips | string | Yes | US state FIPS code (e.g. 06 for California, 36 for New York, * for all states) |
county_fips | string | — | County FIPS code within the state (e.g. 037 for Los Angeles, * for all counties). Omit for state-level data. |
Parameters from the server's own tool schema.
Why census.data.population is rated Low
Retrieves publicly available census data without modification or side effects.
From the tool's definition Get population counts for any US geography by FIPS code — total, male, female.
Attacks that exploit this kind of access
The rule that runs census.data.population 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 census.data.population, this is the rule to start with:
census.data.population 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 census.data.population call is checked against it from then on.
Questions about census.data.population
Get population counts for any US geography by FIPS code — total, male, female. Covers all 50 states, 3,000+ counties, and sub-county areas. Source: American Community Survey 5-year estimates (US Census Bureau). Public domain, updated annually. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
census.data.population accepts 3 parameters: year, state_fips, county_fips. Required: state_fips. 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 census.data.population: 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.
census.data.population 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 census.data.population 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 census.data.population. 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.
census.data.population 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