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

opportunity_zones_lookup_designation

Was this exact 2010 census tract GEOID listed in the final 2018-cycle Qualified Opportunity Zone corpus? Performs an exact lookup against all 8,764 CDFI Fund rows and returns listed/not-listed status, geography, tract type, ACS source, official notices, and provenance. tract_vintage is fixed to 2...

SERVERLivedatalink SOURCEhttps://livedatalink.ai/mcp
Low RISK CLASS
Category Read
Parameters 31 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-lookup-designation.md

What opportunity_zones_lookup_designation does on Livedatalink

AI agents call opportunity_zones_lookup_designation 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
tract_geoid string Yes Exact 11-digit 2010 census tract GEOID: 2-digit state + 3-digit county + 6-digit tract.
tract_vintage integer — Must be 2010. The designation boundaries and identifiers do not change with the 2020 Census.
response_format string — Human-readable markdown or machine-readable JSON. Default markdown.

Parameters from the server's own tool schema.

Why opportunity_zones_lookup_designation is rated Low

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

What does the opportunity_zones_lookup_designation tool do? +

Was this exact 2010 census tract GEOID listed in the final 2018-cycle Qualified Opportunity Zone corpus? Performs an exact lookup against all 8,764 CDFI Fund rows and returns listed/not-listed status, geography, tract type, ACS source, official notices, and provenance. tract_vintage is fixed to 2010: never submit a 2020 tract identifier as if it were equivalent. This is designation evidence, not parcel confirmation or tax/legal advice. 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_lookup_designation accept? +

opportunity_zones_lookup_designation accepts 3 parameters: tract_geoid, tract_vintage, response_format. Required: tract_geoid. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on opportunity_zones_lookup_designation? +

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

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

Can I rate-limit opportunity_zones_lookup_designation? +

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

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

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