edgar_filings_by_form_type
Pull all recent SEC filings of a specific form type across all companies. Useful for monitoring (e.g. 'all 8-Ks today', 'all S-1s this week'). Returns accession numbers, filers, and filing dates.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/edgar-filings-by-form-type.md
What edgar_filings_by_form_type does on Livedatalink
AI agents use edgar_filings_by_form_type to create or update resources in Livedatalink, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Livedatalink environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
limit | number | — | Maximum rows to return (default 25, max 100). |
form_type | string | Yes | SEC form type (e.g. '8-K', 'S-1', 'DEF 14A', '13F-HR'). |
start_date | string | — | ISO date lower bound (YYYY-MM-DD). Defaults to 30 days ago. |
Parameters from the server's own tool schema.
Why edgar_filings_by_form_type is rated Medium
An AI agent can call edgar_filings_by_form_type faster than any human can review: one bad instruction and it creates or modifies resources in Livedatalink by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
The rule that runs edgar_filings_by_form_type 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_filings_by_form_type, this is the rule to start with:
edgar_filings_by_form_type stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. 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_filings_by_form_type call is checked against it from then on.
Questions about edgar_filings_by_form_type
Pull all recent SEC filings of a specific form type across all companies. Useful for monitoring (e.g. 'all 8-Ks today', 'all S-1s this week'). Returns accession numbers, filers, and filing dates. It is categorised as a Write tool in the Livedatalink MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
edgar_filings_by_form_type accepts 3 parameters: limit, form_type, start_date. Required: form_type. 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_filings_by_form_type: 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_filings_by_form_type is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the edgar_filings_by_form_type 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_filings_by_form_type. 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_filings_by_form_type 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