edgar_recent_filings
List recent SEC filings for a company. Filter by form type (10-K, 10-Q, 8-K, 4, DEF 14A, etc.) and start date. Use ticker or CIK as identifier.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/edgar-recent-filings.md
What edgar_recent_filings does on Livedatalink
AI agents call edgar_recent_filings 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 |
|---|---|---|---|
limit | number | — | Maximum rows to return (default 25, max 100). |
form_type | string | — | Optional form type filter (e.g. '10-K', '10-Q', '8-K', '4'). |
identifier | string | Yes | Ticker symbol or CIK. Examples: 'AAPL', '0000320193'. |
start_date | string | — | Optional ISO date lower bound (YYYY-MM-DD). |
Parameters from the server's own tool schema.
Why edgar_recent_filings is rated Low
This tool retrieves publicly available SEC filing data. It only reads/lists information from EDGAR with no side effects, modifications, or destructive actions possible.
From the tool's definition List recent SEC filings for a company... Filter by form type... Use ticker or CIK as identifier
Attacks that exploit this kind of access
The rule that runs edgar_recent_filings 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_recent_filings, this is the rule to start with:
edgar_recent_filings 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_recent_filings call is checked against it from then on.
Questions about edgar_recent_filings
List recent SEC filings for a company. Filter by form type (10-K, 10-Q, 8-K, 4, DEF 14A, etc.) and start date. Use ticker or CIK as identifier. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
edgar_recent_filings accepts 4 parameters: limit, form_type, identifier, start_date. Required: identifier. 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_recent_filings: 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_recent_filings 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_recent_filings 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_recent_filings. 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_recent_filings 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