opportunity_zones_search_designations

SERVERLivedatalink SOURCEhttps://livedatalink.ai/mcp

Low RISK CLASS

Category Read

Parameters 70 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/opportunity-zones-search-designations.md

WHAT IT DOES

What opportunity_zones_search_designations does on Livedatalink

AI agents call opportunity_zones_search_designations 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	—	Maximum designations. Default 20.
`query`	string	—	Words matched against exact 2010 GEOID, state name/code, or county name.
`county`	string	—	Exact county/county-equivalent name within the optional jurisdiction.
`offset`	integer	—	Designations to skip. Default 0.
`tract_type`	string	—	Official tract type in the designation workbook.
`jurisdiction`	string	—	Exact state/territory name, USPS abbreviation, or two-digit state FIPS in the 2018 designation corpus.
`response_format`	string	—	Human-readable markdown or machine-readable JSON. Default markdown.

Parameters from the server's own tool schema.

RISK

Why opportunity_zones_search_designations is rated Low

Even though opportunity_zones_search_designations 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

RECOMMENDED RULE

The rule that runs opportunity_zones_search_designations 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 opportunity_zones_search_designations, this is the rule to start with:

opportunity_zones_search_designations Allowed

opportunity_zones_search_designations is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "opportunity_zones_search_designations": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Livedatalink, apply this rule, and every opportunity_zones_search_designations call is checked against it from then on.

FAQ

Questions about opportunity_zones_search_designations

What does the opportunity_zones_search_designations tool do? +

Which final 2018-cycle Qualified Opportunity Zone designations match a tract, county, or jurisdiction? Searches the complete self-hosted CDFI Fund designation workbook with optional jurisdiction, county, and official tract-type filters. Returns bounded, paginated rows with 2010 GEOIDs, source hash, IRS authority, and a 2010-versus-2020 boundary warning. Use for discovery; do not use a 2020-vintage GEOID or treat this archived final cycle as the still-unfinalized 2027 cycle. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.

What parameters does opportunity_zones_search_designations accept? +

opportunity_zones_search_designations accepts 7 parameters: limit, query, county, offset, tract_type, jurisdiction, response_format. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on opportunity_zones_search_designations? +

Register the Livedatalink MCP server in PolicyLayer and add a rule for opportunity_zones_search_designations: 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 opportunity_zones_search_designations? +

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

Can I rate-limit opportunity_zones_search_designations? +

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

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

opportunity_zones_search_designations 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.

KEEP EXPLORING

More on Livedatalink, and thousands of servers like it.

This server

All 381 Livedatalink tools →

Across the catalogue

binary_search on 010 Editor →evaluate_search_quality on ACE-MCP →search_torrents on M-Team MCP Server →aiva_search_customers on AIVA MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →