hud_lihtc_year15_radar
Find HUD LIHTC properties whose placed-in-service year reaches the federal 15-year reference date in an exact window. Returns source project fields, unit counts, and a clearly labeled screening date. Use this for 'LIHTC projects reaching year 15 in 2027'. Year 15 is not proof that affordability r...
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/hud-lihtc-year15-radar.md
What hud_lihtc_year15_radar does on Livedatalink
AI agents call hud_lihtc_year15_radar 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.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | integer | — | |
state | string | — | |
offset | integer | — | |
end_date | string | Yes | Inclusive YYYY-MM-DD window end. |
min_units | integer | — | |
start_date | string | Yes | Inclusive YYYY-MM-DD window start. |
response_format | string | — | Human-readable markdown or machine-readable JSON. Default markdown. |
Parameters from the server's own tool schema.
Why hud_lihtc_year15_radar is rated Low
Even though hud_lihtc_year15_radar 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.
Attacks that exploit this kind of access
The rule that runs hud_lihtc_year15_radar safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Livedatalink, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For hud_lihtc_year15_radar, this is the rule to start with:
hud_lihtc_year15_radar is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Livedatalink, apply this rule, and every hud_lihtc_year15_radar call is checked against it from then on.
Questions about hud_lihtc_year15_radar
Find HUD LIHTC properties whose placed-in-service year reaches the federal 15-year reference date in an exact window. Returns source project fields, unit counts, and a clearly labeled screening date. Use this for 'LIHTC projects reaching year 15 in 2027'. Year 15 is not proof that affordability restrictions expire; extended-use rules vary by state and property documents, so this is not legal, compliance, or investment advice. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
hud_lihtc_year15_radar accepts 7 parameters: limit, state, offset, end_date, min_units, start_date, response_format. Required: end_date, start_date. The full parameter table on this page comes from the server's own tool schema.
Register the Livedatalink MCP server in PolicyLayer and add a rule for hud_lihtc_year15_radar: 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.
hud_lihtc_year15_radar 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 hud_lihtc_year15_radar 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 hud_lihtc_year15_radar. 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.
hud_lihtc_year15_radar 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.
This server
Across the catalogue