Compare employment data for multiple areas side by side (2-10 areas). All geoids must share the same area type. Returns per-area metrics including total jobs, industry mix, earnings, and age breakdown.
AI agents call compare_employment 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. |
geoids | string | Yes | Comma-separated FIPS codes to compare (2-10). All must match the specified area type. |
area_type | string | Yes | Geographic level shared by all geoids. |
perspective | string | — | workplace (default) or residence. |
Parameters from the server's own tool schema.
This tool queries and retrieves employment statistics for geographic areas and returns comparative data. The action is purely informational—it reads existing employment data and presents it side-by-side for analysis. There are no side effects, no data modification, no code execution, and no destructive operations.
From the tool's definition Tool name 'compare_employment' and description states it 'Compare employment data' and 'Returns per-area metrics' - purely retrieval and analysis operations with no modification, deletion, or execution of external systems.
Attacks that exploit this kind of access
Compare employment data for multiple areas side by side (2-10 areas). All geoids must share the same area type. Returns per-area metrics including total jobs, industry mix, earnings, and age breakdown. It is categorised as a Read tool in the loc8n Geographic Data MCP Server, which means it retrieves data without modifying state.
compare_employment accepts 4 parameters: year, geoids, area_type, perspective. Required: geoids, area_type. 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 compare_employment: 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.
compare_employment 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 compare_employment 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 compare_employment. 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.
compare_employment 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.
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 →