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

opportunity_zones_compare_jurisdictions

Which of 2-10 requested states or territories has more final 2018-cycle QOZ designations? Resolves exact jurisdiction selectors and compares total, Low-Income Community, Non-LIC Contiguous, and covered county counts, sorted by total. Includes complete-corpus provenance and tract-vintage/cycle war...

SERVERLivedatalink SOURCEhttps://livedatalink.ai/mcp
Low RISK CLASS
Category Read
Parameters 21 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-compare-jurisdictions.md

What opportunity_zones_compare_jurisdictions does on Livedatalink

AI agents call opportunity_zones_compare_jurisdictions 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
jurisdictions array Yes Two to ten distinct state/territory selectors.
response_format string — Human-readable markdown or machine-readable JSON. Default markdown.

Parameters from the server's own tool schema.

Why opportunity_zones_compare_jurisdictions is rated Low

Even though opportunity_zones_compare_jurisdictions 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_compare_jurisdictions

What does the opportunity_zones_compare_jurisdictions tool do? +

Which of 2-10 requested states or territories has more final 2018-cycle QOZ designations? Resolves exact jurisdiction selectors and compares total, Low-Income Community, Non-LIC Contiguous, and covered county counts, sorted by total. Includes complete-corpus provenance and tract-vintage/cycle warnings. It compares designation counts, not investment quality, land area, population, current eligibility, or the pending 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_compare_jurisdictions accept? +

opportunity_zones_compare_jurisdictions accepts 2 parameters: jurisdictions, response_format. Required: jurisdictions. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on opportunity_zones_compare_jurisdictions? +

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

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

Can I rate-limit opportunity_zones_compare_jurisdictions? +

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

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

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