counterparty_risk_score

SERVERLivedatalink SOURCEhttps://livedatalink.ai/mcp

Low RISK CLASS

Category Read

Parameters 11 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/counterparty-risk-score.md

WHAT IT DOES

What counterparty_risk_score does on Livedatalink

AI agents call counterparty_risk_score 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
`company_name`	string	Yes	Company or entity name to score. Examples: 'Lockheed Martin', 'Acme Holdings BV', 'Pfizer Inc'. Common suffixes (Inc/LLC/Ltd/Corp) are normalized automatically.

Parameters from the server's own tool schema.

RISK

Why counterparty_risk_score is rated Low

This tool retrieves and queries data from multiple external sources (sanctions lists, regulatory filings, court records, environmental databases, federal spending records) and synthesizes them into a risk assessment. No write, execute, destructive, or financial operations are performed. The tool does not modify data, execute code on behalf of the user, delete anything, or move money.

From the tool's definition Tool description states it 'Compute[s] a composite 0-100 Counterparty Risk Score' by querying and aggregating data from sanctions databases (OFAC/UN/EU/BIS), SEC EDGAR, federal courts, EPA ECHO, and USAspending.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

counterparty_risk_score Allowed

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

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

FAQ

Questions about counterparty_risk_score

What does the counterparty_risk_score tool do? +

Compute a composite 0-100 Counterparty Risk Score for a company name. Combines findings from sanctions screening (OFAC/UN/EU/BIS), SEC EDGAR (registered-filer signal), federal courts (litigation history), EPA ECHO (environmental enforcement), and USAspending (federal contract vetting) into a single weighted metric with an explainable evidence chain. Returns: score, risk band (clean/low/moderate/elevated/high/critical), itemized evidence with citations, sources queried, sources that failed, and a plain-text summary suitable for an AI agent to surface to a user. Sanctions hits zero the score regardless of other signals. Use this when you need a single-call counterparty risk verdict instead of stitching five separate queries. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.

What parameters does counterparty_risk_score accept? +

counterparty_risk_score accepts 1 parameter: company_name. Required: company_name. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on counterparty_risk_score? +

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

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

Can I rate-limit counterparty_risk_score? +

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

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

counterparty_risk_score 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 →