issuer_diligence_dossier

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/issuer-diligence-dossier.md

WHAT IT DOES

What issuer_diligence_dossier does on Livedatalink

AI agents call issuer_diligence_dossier 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 hint for disambiguation (currently informational).
`ticker`	string	—	Optional stock ticker hint to pin the SEC EDGAR match (e.g. 'LMT').
`company`	string	Yes	Public company / SEC issuer name (e.g. 'Lockheed Martin', 'Pfizer').

Parameters from the server's own tool schema.

RISK

Why issuer_diligence_dossier is rated Low

Even though issuer_diligence_dossier 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.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

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

issuer_diligence_dossier Allowed

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

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

FAQ

Questions about issuer_diligence_dossier

What does the issuer_diligence_dossier tool do? +

One-call NARRATIVE public-record diligence dossier for a public company / SEC issuer. Joins SEC EDGAR (registrant identity, CIK/ticker, recent filings and their form mix), federal courts via CourtListener (RECAP dockets whose name references the issuer), USAspending (federal contract awards, name-matched), and CPSC product-safety recalls into a readable brief with a short headline and four sections: Identity & SEC, Litigation, Federal business, and Product-safety. Every source degrades gracefully - a failing leg is noted, not fatal. This is a narrative synthesis, deliberately distinct from counterparty_risk_score (a 0-100 score) and entity_dossier (SEC+EPA+sanctions only). Informational public-record synthesis, not a background check or legal/financial advice. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.

What parameters does issuer_diligence_dossier accept? +

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

How do I enforce a policy on issuer_diligence_dossier? +

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

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

Can I rate-limit issuer_diligence_dossier? +

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

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

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