fcc.geo.block_fips
Look up the US Census Block FIPS code, county FIPS, and state for any US latitude/longitude coordinate using the FCC Census Block API. Returns the 15-digit Block FIPS (state + county + tract + block), bounding box, county name, and state code. Useful for determining which regulatory jurisdiction,...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/fcc.geo.block-fips.md
What fcc.geo.block_fips does on Apibase
AI agents call fcc.geo.block_fips 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 |
|---|---|---|---|
latitude | number | Yes | Latitude of the location (e.g. 38.9072). |
longitude | number | Yes | Longitude of the location (e.g. -77.0369). |
census_year | string | — | Census year for block boundaries: "2000", "2010", or "2020" (default current). |
Parameters from the server's own tool schema.
Why fcc.geo.block_fips is rated Low
Retrieves geographic and census data for coordinates; no modification or execution of external operations.
From the tool's definition Look up, returns, no API key required, no side effects
Attacks that exploit this kind of access
The rule that runs fcc.geo.block_fips 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 fcc.geo.block_fips, this is the rule to start with:
fcc.geo.block_fips 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 fcc.geo.block_fips call is checked against it from then on.
Questions about fcc.geo.block_fips
Look up the US Census Block FIPS code, county FIPS, and state for any US latitude/longitude coordinate using the FCC Census Block API. Returns the 15-digit Block FIPS (state + county + tract + block), bounding box, county name, and state code. Useful for determining which regulatory jurisdiction, broadband program, or census reporting area a location falls within. No API key required. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
fcc.geo.block_fips accepts 3 parameters: latitude, longitude, census_year. Required: latitude, longitude. 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 fcc.geo.block_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 Apibase. Nothing to install.
fcc.geo.block_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 fcc.geo.block_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 fcc.geo.block_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.
fcc.geo.block_fips 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