Get FIPS codes for a geography level. Useful for finding state/county codes.
AI agents call get_fips to retrieve information from Census API MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a straightforward lookup operation against public U.S. Census geographic identifiers. FIPS codes are reference data that are not sensitive, widely published by the government, and retrieving them has no side effects. The tool simply returns existing data without modifying, executing operations, or causing irreversible changes. This is a classic Read category operation.
From the tool's definition The tool retrieves FIPS codes by querying existing geographic reference data. The description states it is useful for 'finding' codes, and the function name pattern 'get_' indicates data retrieval.
Attacks that exploit this kind of access
Get FIPS codes for a geography level. Useful for finding state/county codes. It is categorised as a Read tool in the Census API MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Census API MCP Server MCP server in PolicyLayer and add a rule for get_fips: 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 Census API MCP Server. Nothing to install.
get_fips 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 get_fips 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 get_fips. 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.
get_fips is provided by the Census API MCP Server MCP server (shawndrake2/mcp-census). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →