Get Point-in-Time (PIT) homeless count data by Continuum of Care region. Returns homeless population counts from the annual PIT count, broken down by sheltered/unsheltered status and sub-populations. Data sourced from HUD Exchange via ArcGIS open data. No API key required. Args: state: Two-letter...
Part of the HUD Housing Data server.
Free to start. No card required.
AI agents call get_homeless_data to retrieve information from HUD Housing Data without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though get_homeless_data only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"get_homeless_data": {}
}
}See the full HUD Housing Data policy for all 5 tools.
These attack patterns abuse exactly the kind of access get_homeless_data gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
Get Point-in-Time (PIT) homeless count data by Continuum of Care region. Returns homeless population counts from the annual PIT count, broken down by sheltered/unsheltered status and sub-populations. Data sourced from HUD Exchange via ArcGIS open data. No API key required. Args: state: Two-letter US state abbreviation (e.g. 'CA', 'WA'). At least one of state or coc_code must be provided. coc_code: Optional Continuum of Care code (e.g. 'WA-500', 'CA-600'). year: Optional year to filter results.. It is categorised as a Read tool in the HUD Housing Data MCP Server, which means it retrieves data without modifying state.
Register the HUD Housing Data MCP server in PolicyLayer and add a rule for get_homeless_data: 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 HUD Housing Data. Nothing to install.
get_homeless_data 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_homeless_data 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_homeless_data. 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_homeless_data is provided by the HUD Housing Data MCP server (https://mcp.olyport.com/hud-housing/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 5 HUD Housing Data tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.