edgar_filing_content
Fetch the text content of a specific SEC filing. Returns the primary document (10-K, 10-Q, etc.) stripped of HTML, suitable for LLM consumption. Use edgar_recent_filings first to get the accession number.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/edgar-filing-content.md
What edgar_filing_content does on Livedatalink
AI agents call edgar_filing_content 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 |
|---|---|---|---|
cik | string | Yes | Filer CIK (with or without leading zeros). |
max_chars | number | — | Maximum characters of text to return (default 20000, max 200000). |
accession_number | string | Yes | Accession number (e.g. '0000320193-25-000006' or '000032019325000006'). |
Parameters from the server's own tool schema.
Why edgar_filing_content is rated Low
This tool retrieves and returns existing public financial documents from the SEC's EDGAR database. It performs a read-only query operation with no side effects, data modification, or destructive capabilities. The information accessed is already public. The 'low' severity reflects minimal risk even if misused, as the tool only exposes already-disclosed corporate filings.
From the tool's definition Tool description states 'Fetch the text content' and 'Returns the primary document', indicating data retrieval with no modification or deletion.
Attacks that exploit this kind of access
The rule that runs edgar_filing_content 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 edgar_filing_content, this is the rule to start with:
edgar_filing_content 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 edgar_filing_content call is checked against it from then on.
Questions about edgar_filing_content
Fetch the text content of a specific SEC filing. Returns the primary document (10-K, 10-Q, etc.) stripped of HTML, suitable for LLM consumption. Use edgar_recent_filings first to get the accession number. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
edgar_filing_content accepts 3 parameters: cik, max_chars, accession_number. Required: cik, accession_number. 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 edgar_filing_content: 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.
edgar_filing_content 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 edgar_filing_content 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 edgar_filing_content. 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.
edgar_filing_content 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