New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

fhfa_hpi_compare

Compare two to eight US geographies on a consistent FHFA HPI series and rank them by one-year price-index change. Returns latest level, one-year and five-year change, CAGR, recent direction, stable place_id/geography_level fields, and source provenance for later property-market evidence packs. Us...

SERVERLivedatalink SOURCEhttps://livedatalink.ai/mcp
Low RISK CLASS
Category Read
Parameters 61 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/fhfa-hpi-compare.md

What fhfa_hpi_compare does on Livedatalink

AI agents call fhfa_hpi_compare to retrieve information from Livedatalink without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

ParameterTypeRequiredDescription
places array Yes Two to eight exact FHFA place ids or geography names.
frequency string — Observation frequency. Default quarterly.
hpi_flavor string — FHFA index flavor. Default purchase-only.
index_basis string — Index column to use. Default seasonally_adjusted.
geography_level string — Optional exact FHFA geography level to disambiguate state, metro, division, or national series.
response_format string — Human-readable markdown or machine-readable JSON. Default markdown.

Parameters from the server's own tool schema.

Why fhfa_hpi_compare is rated Low

Even though fhfa_hpi_compare only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Questions about fhfa_hpi_compare

What does the fhfa_hpi_compare tool do? +

Compare two to eight US geographies on a consistent FHFA HPI series and rank them by one-year price-index change. Returns latest level, one-year and five-year change, CAGR, recent direction, stable place_id/geography_level fields, and source provenance for later property-market evidence packs. Use this for 'compare home-price momentum in Texas and Florida' or 'which of these metros has stronger five-year appreciation?'. Not a property valuation or investment recommendation. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.

What parameters does fhfa_hpi_compare accept? +

fhfa_hpi_compare accepts 6 parameters: places, frequency, hpi_flavor, index_basis, geography_level, response_format. Required: places. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on fhfa_hpi_compare? +

Register the Livedatalink MCP server in PolicyLayer and add a rule for fhfa_hpi_compare: 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 Livedatalink. Nothing to install.

What risk level is fhfa_hpi_compare? +

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

Can I rate-limit fhfa_hpi_compare? +

Yes. Add a rate_limit block to the fhfa_hpi_compare 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 fhfa_hpi_compare completely? +

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

fhfa_hpi_compare is provided by the Livedatalink MCP server (https://livedatalink.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on Livedatalink, and thousands of servers like it.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Livedatalink's. Pull the full record:

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.