environmental_site_risk

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/environmental-site-risk.md

WHAT IT DOES

What environmental_site_risk does on Livedatalink

AI agents call environmental_site_risk 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
`site`	string	Yes	Site, facility, or operator name to screen (e.g. 'Smith Manufacturing', 'Acme Plating Inc').
`state`	string	—	Optional 2-letter state to disambiguate the EPA facility and parcel search.
`address`	string	—	Optional street address to pin the parcel record.

Parameters from the server's own tool schema.

RISK

Why environmental_site_risk is rated Low

Even though environmental_site_risk 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 environmental_site_risk 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 environmental_site_risk, this is the rule to start with:

environmental_site_risk Allowed

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

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

FAQ

Questions about environmental_site_risk

What does the environmental_site_risk tool do? +

One-call environmental-compliance and contamination liability read for a SPECIFIC site or operator - the question a buyer, lender, or Phase-I ESA asks before a deal. Distinct from location_risk_report (which scores natural hazards plus a shallow count of nearby facilities): this drills DEEP into one named facility's EPA record via ECHO/FRS - overall compliance status, per-statute program standing (Clean Air/Water/RCRA/etc.), formal enforcement actions and penalty totals, significant-non-compliance and non-compliant-quarter flags - plus a best-effort parcel record for site context. Returns a verdict band (NO ADVERSE EPA RECORD / REVIEW RECOMMENDED / CONTAMINATION-COMPLIANCE CONCERN / NO FACILITY FOUND), the flags, and the evidence. A source that fails is noted, not fatal. This is an EPA public-record screen, not a Phase-I Environmental Site Assessment or a substitute for one. Premium cross-source synthesis. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.

What parameters does environmental_site_risk accept? +

environmental_site_risk accepts 3 parameters: site, state, address. Required: site. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on environmental_site_risk? +

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

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

Can I rate-limit environmental_site_risk? +

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

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

environmental_site_risk 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

aiva_get_churn_risk on AIVA MCP Server → The MCP Attack Database →

Guides

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