get_migration_trends

Retrieve migration summary data across all available year pairs for a county or state. Returns an array of yearly migration summaries sorted by year pair, each including net returns, net exemptions, net AGI, and inflow/outflow breakdowns. AGI values are in thousands of dollars. Source: IRS Statis...

Server loc8n Geographic Data gener8v/gener8v.mcp.geographic-data
Category Read
Risk class Low
Parameters 22 required

What get_migration_trends does on loc8n Geographic Data

AI agents call get_migration_trends 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.

ParameterTypeRequiredDescription
fips string Yes FIPS code — 5 digits for county, 2 for state
level string Yes Geographic level: county or state

Parameters from the server's own tool schema.

Why get_migration_trends needs a policy

This tool performs a straightforward data retrieval of aggregate migration and demographic statistics (net returns, exemptions, AGI, inflow/outflow). It has no side effects, cannot modify data, execute code, or trigger external operations. The AGI values returned are aggregated public statistics, not sensitive personal financial information.

From the tool's definition Tool name is 'get_migration_trends' and description states it 'Retrieve[s] migration summary data' — a read operation that queries historical migration statistics from IRS data without any create, modify, delete, or execute actions.

Questions about get_migration_trends

What does the get_migration_trends tool do? +

Retrieve migration summary data across all available year pairs for a county or state. Returns an array of yearly migration summaries sorted by year pair, each including net returns, net exemptions, net AGI, and inflow/outflow breakdowns. AGI values are in thousands of dollars. Source: IRS Statistics of Income. It is categorised as a Read tool in the loc8n Geographic Data MCP Server, which means it retrieves data without modifying state.

What parameters does get_migration_trends accept? +

get_migration_trends accepts 2 parameters: fips, level. Required: fips, level. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on get_migration_trends? +

Register the loc8n Geographic Data MCP server in PolicyLayer and add a rule for get_migration_trends: 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.

What risk level is get_migration_trends? +

get_migration_trends is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_migration_trends? +

Yes. Add a rate_limit block to the get_migration_trends 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.

How do I block get_migration_trends completely? +

Set action: deny in the PolicyLayer policy for get_migration_trends. 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.

What MCP server provides get_migration_trends? +

get_migration_trends 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.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.