supplier_esg_scorecard
One-call, resale-safe ESG / supplier-risk read for a company - no proprietary ESG-rating license needed. Joins three public-record governance-signal legs: EPA ECHO/FRS environmental compliance (significant-non-compliance flags, non-compliant quarters, penalties, and formal enforcement actions acr...
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/supplier-esg-scorecard.md
What supplier_esg_scorecard does on Livedatalink
AI agents call supplier_esg_scorecard 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 |
|---|---|---|---|
state | string | — | Optional 2-letter state to disambiguate the EPA facility search (e.g. 'PA'). |
company | string | Yes | Company / supplier name to score (e.g. 'US Steel', 'Tyson Foods'). |
Parameters from the server's own tool schema.
Why supplier_esg_scorecard is rated Low
Even though supplier_esg_scorecard 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
The rule that runs supplier_esg_scorecard 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 supplier_esg_scorecard, this is the rule to start with:
supplier_esg_scorecard is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Livedatalink, apply this rule, and every supplier_esg_scorecard call is checked against it from then on.
Questions about supplier_esg_scorecard
One-call, resale-safe ESG / supplier-risk read for a company - no proprietary ESG-rating license needed. Joins three public-record governance-signal legs: EPA ECHO/FRS environmental compliance (significant-non-compliance flags, non-compliant quarters, penalties, and formal enforcement actions across the company's facilities, with correct filtering so clean 'No Violation Identified' statuses are never flagged), product recalls (CPSC consumer products + openFDA drug/device/food, keyed by the company), and federal-court litigation (CourtListener v4 dockets whose caption actually names the company). Returns a readable scorecard across Environmental / Product-safety / Litigation dimensions with a rolled-up read (LOW / MODERATE / ELEVATED ESG risk signals) and the evidence behind each. A leg that fails is noted, not fatal. This is informational public-record synthesis of ESG/supplier-risk SIGNALS, NOT an ESG rating, credit/background report, or investment advice. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
supplier_esg_scorecard accepts 2 parameters: state, company. Required: company. The full parameter table on this page comes from the server's own tool schema.
Register the Livedatalink MCP server in PolicyLayer and add a rule for supplier_esg_scorecard: 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.
supplier_esg_scorecard is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the supplier_esg_scorecard 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.
Set action: deny in the PolicyLayer policy for supplier_esg_scorecard. 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.
supplier_esg_scorecard 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.
This server
Across the catalogue