Compare mortgage lending metrics across 2-5 geographic areas for a single HMDA data year. All areas must be the same geographic level (tract, county, or state). Returns side-by-side summaries including origination count, denial rate, median loan amount, and loan type/purpose breakdowns for each a...
AI agents call compare_mortgage 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 | — | HMDA data year (default: most recent available) |
geoids | array | Yes | Array of 2-5 FIPS codes to compare |
area_type | string | Yes | Geographic level (must be same for all areas): tract (or census_tract), county, or state |
Parameters from the server's own tool schema.
This tool retrieves and compares mortgage lending data across geographic areas. It performs no side effects—no data is created, modified, deleted, or used to trigger external operations. The tool simply queries CFPB/FFIEC HMDA databases and returns analytical summaries.
From the tool's definition Tool description uses 'compare' and 'returns side-by-side summaries' indicating data retrieval only. HMDA mortgage metrics are queried and presented without modification, deletion, or execution of external operations.
Attacks that exploit this kind of access
Compare mortgage lending metrics across 2-5 geographic areas for a single HMDA data year. All areas must be the same geographic level (tract, county, or state). Returns side-by-side summaries including origination count, denial rate, median loan amount, and loan type/purpose breakdowns for each area. Source: CFPB/FFIEC HMDA. It is categorised as a Read tool in the loc8n Geographic Data MCP Server, which means it retrieves data without modifying state.
compare_mortgage accepts 3 parameters: year, geoids, area_type. 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_mortgage: 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_mortgage 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_mortgage 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_mortgage. 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_mortgage 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 →