Low Risk

get_lending_by_race

Get mortgage lending patterns disaggregated by race and ethnicity. Returns mortgage origination and denial data broken down by the race/ethnicity of the applicant. Useful for fair lending analysis and identifying disparities in mortgage access. Args: state: Two-letter US state abbreviation (e.g. ...

Part of the HMDA Mortgage Data server.

get_lending_by_race is read-only, but an agent in a loop can still rack up calls and cost. PolicyLayer caps every call before it runs. Live in minutes.

SECURE HMDA MORTGAGE DATA →

Free to start. No card required.

AI agents call get_lending_by_race to retrieve information from HMDA Mortgage 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_lending_by_race 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.

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_lending_by_race": {}
  }
}

See the full HMDA Mortgage Data policy for all 4 tools.

Get this rule live on your own HMDA Mortgage Data server in minutes. PolicyLayer enforces it on every call, before it runs.

ENFORCE ON MY HMDA MORTGAGE DATA →

These attack patterns abuse exactly the kind of access get_lending_by_race gives an agent. Each links to the full case and the policy that stops it:

Browse the full MCP Attack Database →

Every attack above starts with a tool call. PolicyLayer checks each one against your policy first, so get_lending_by_race only ever does what you allow.

SECURE HMDA MORTGAGE DATA →

Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.

What does the get_lending_by_race tool do? +

Get mortgage lending patterns disaggregated by race and ethnicity. Returns mortgage origination and denial data broken down by the race/ethnicity of the applicant. Useful for fair lending analysis and identifying disparities in mortgage access. Args: state: Two-letter US state abbreviation (e.g. 'CA', 'TX'). county_fips: Five-digit county FIPS code (e.g. '06037' for LA County). year: Data year (e.g. 2022). Defaults to 2022 if not specified.. It is categorised as a Read tool in the HMDA Mortgage Data MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_lending_by_race? +

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

What risk level is get_lending_by_race? +

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

Can I rate-limit get_lending_by_race? +

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

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

get_lending_by_race is provided by the HMDA Mortgage Data MCP server (https://mcp.olyport.com/hmda/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every HMDA Mortgage Data tool call.

Deterministic rules across all 4 HMDA Mortgage 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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.