Retrieve commute flow (origin-destination) data for a county or state. Shows where workers come from (inbound) or where residents commute to (outbound). Returns top flow pairs with job counts and a 3-supersector industry breakdown (Goods Producing, Trade/Transport/Utilities, All Other Services). ...
AI agents call get_commute_flows to retrieve information from loc8n Geographic Data without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
year | integer | — | Data year. Omit to use the most recent available year. |
geoid | string | Yes | FIPS code — 5 digits for county, 2 for state. |
limit | integer | — | Number of top flow pairs to return (1-100, default 25). |
min_jobs | integer | — | Minimum job count threshold to include a flow pair (default 0). |
area_type | string | Yes | Geographic level: county or state (tract is not supported for flows). |
direction | string | Yes | inbound = where workers come from; outbound = where residents commute to. |
Parameters from the server's own tool schema.
This tool only queries and retrieves existing geographic and employment commute data from the loc8n API. It performs no writes, deletions, code execution, or financial operations. The data returned is informational demographic/employment statistics. Even if misused by an AI agent, it cannot modify data, trigger external actions, or cause financial harm—only retrieve information that is presumably public U.S.
From the tool's definition Tool description states 'Retrieve commute flow (origin-destination) data' and 'Returns top flow pairs with job counts and industry breakdown'.
Attacks that exploit this kind of access
Retrieve commute flow (origin-destination) data for a county or state. Shows where workers come from (inbound) or where residents commute to (outbound). Returns top flow pairs with job counts and a 3-supersector industry breakdown (Goods Producing, Trade/Transport/Utilities, All Other Services). Note: this uses OD data with a coarser industry breakdown than the 20-sector NAICS detail available in single-area employment summaries. Not available at the tract level. It is categorised as a Read tool in the loc8n Geographic Data MCP Server, which means it retrieves data without modifying state.
get_commute_flows accepts 6 parameters: year, geoid, limit, min_jobs, area_type, direction. Required: geoid, area_type, direction. The full parameter table on this page comes from the server's own tool schema.
Register the loc8n Geographic Data MCP server in PolicyLayer and add a rule for get_commute_flows: 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 loc8n Geographic Data. Nothing to install.
get_commute_flows 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_commute_flows 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_commute_flows. 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_commute_flows is provided by the loc8n Geographic Data MCP server (gener8v/gener8v.mcp.geographic-data). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
get_commute_flows is one line of loc8n Geographic Data's registry record.
The record carries the whole server: verified identity, auth posture, risk grade, every tool classified, recommended policy — re-checked continuously.
Teams ship this data inside their own products. See what a licence covers →