Retrieve Fair Market Rent data across multiple years for a single area. Returns an array of yearly FMR records with rent values by bedroom count. Supports ZIP, county, and CBSA area types. State-level trends are not supported because state queries return aggregated lists of ZIP-level records, not...
AI agents call get_fmr_trend 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 |
|---|---|---|---|
end_year | integer | — | Last year of the range (default: latest available) |
area_code | string | Yes | Area identifier — format depends on area_type |
area_type | string | Yes | Geographic area type: zip, county, or cbsa (state is not supported for trends) |
start_year | integer | — | First year of the range (default: earliest available) |
Parameters from the server's own tool schema.
This tool retrieves historical Fair Market Rent (FMR) data from HUD for demographic and housing analysis. It queries a dataset and returns time-series rent values—a classic read operation with no side effects. The tool cannot modify data, execute commands, delete records, or initiate financial transactions. The data returned is informational reference material used for analysis and planning.
From the tool's definition Tool description states 'Retrieve Fair Market Rent data' and 'Returns an array of yearly FMR records'. The verb 'Retrieve' combined with 'Returns data' indicates a read-only query operation with no modification or execution of external actions.
Attacks that exploit this kind of access
Retrieve Fair Market Rent data across multiple years for a single area. Returns an array of yearly FMR records with rent values by bedroom count. Supports ZIP, county, and CBSA area types. State-level trends are not supported because state queries return aggregated lists of ZIP-level records, not a single time series. Source: U.S. Dept. of Housing & Urban Development, Fair Market Rents. It is categorised as a Read tool in the loc8n Geographic Data MCP Server, which means it retrieves data without modifying state.
get_fmr_trend accepts 4 parameters: end_year, area_code, area_type, start_year. Required: area_code, 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 get_fmr_trend: 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_fmr_trend 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_fmr_trend 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_fmr_trend. 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_fmr_trend 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 →