parcel_coverage

List which states/counties the parcel tools currently cover and how many parcels each holds. Coverage grows by state over time.

SERVERLivedatalink SOURCEhttps://livedatalink.ai/mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/parcel-coverage.md

WHAT IT DOES

What parcel_coverage does on Livedatalink

AI agents call parcel_coverage 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.

RISK

Why parcel_coverage is rated Low

The tool performs a query to display informational data about geographic coverage and parcel counts. There is no data creation, modification, deletion, code execution, or financial transaction involved. It is purely a lookup/list operation with no harmful potential if misused by an AI agent.

From the tool's definition Tool name is 'parcel_coverage' and description states 'List which states/counties the parcel tools currently cover' — this is a read-only operation that retrieves coverage metadata without modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

parcel_coverage Allowed

parcel_coverage 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": {
    "parcel_coverage": {}
  }
}

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 parcel_coverage call is checked against it from then on.

FAQ

Questions about parcel_coverage

What does the parcel_coverage tool do? +

List which states/counties the parcel tools currently cover and how many parcels each holds. Coverage grows by state over time. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on parcel_coverage? +

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

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

Can I rate-limit parcel_coverage? +

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

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

parcel_coverage 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 280 Livedatalink tools →

Across the catalogue

The MCP Attack Database →

Guides

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