search_8k_filings
Search recent SEC 8-K filings (current report) from the past 72 hours. Args: items: Comma-separated 8-K item codes to filter on. Examples: '1.05' (cybersecurity), '5.02' (officer departure), '8.01' (other events), '1.01' (material agreement). Leave None for all 8-Ks. suspected_buried_only: If Tru...
This record as markdown: /tools/com-filingfirehose-firehose/search-8k-filings.md
What search_8k_filings does on FilingFirehose
AI agents call search_8k_filings to retrieve information from FilingFirehose 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 |
|---|---|---|---|
items | object | — | |
limit | integer | — | |
suspected_buried_only | boolean | — |
Parameters from the server's own tool schema.
Why search_8k_filings is rated Low
This tool retrieves and queries publicly available SEC EDGAR filings with optional filtering. It has no side effects—it neither creates, modifies, deletes, executes code, nor commits financial transactions. The classifier analysis is metadata enrichment for the search results, not an operation on external systems.
From the tool's definition Tool name 'search_8k_filings' and description 'Search recent SEC 8-K filings' indicate pure data retrieval with no modification. Arguments are filters (item codes, classification flags) that narrow query scope. Returns filing data only.
Attacks that exploit this kind of access
The rule that runs search_8k_filings safely
PolicyLayer is an MCP gateway: it sits between your AI agents and FilingFirehose, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For search_8k_filings, this is the rule to start with:
search_8k_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 FilingFirehose, apply this rule, and every search_8k_filings call is checked against it from then on.
Questions about search_8k_filings
Search recent SEC 8-K filings (current report) from the past 72 hours. Args: items: Comma-separated 8-K item codes to filter on. Examples: '1.05' (cybersecurity), '5.02' (officer departure), '8.01' (other events), '1.01' (material agreement). Leave None for all 8-Ks. suspected_buried_only: If True, return only filings where our body-text classifier flagged a suspected misclassification — i.e. cyber language under Item 8.01 that should have been 1.05, officer-departure language under 8.01 that should have been 5.02. limit: Max results (1-50, default 25). Returns: JSON-formatted list of filings. Each includes: accession_number, company_name, filed_at, filer_reported_items, detected_items, discrepancy_items (in body but not reported), and suspected_buried_events (map of reported→suspected). It is categorised as a Read tool in the FilingFirehose MCP Server, which means it retrieves data without modifying state.
search_8k_filings accepts 3 parameters: items, limit, suspected_buried_only. The full parameter table on this page comes from the server's own tool schema.
Register the FilingFirehose MCP server in PolicyLayer and add a rule for search_8k_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 FilingFirehose. Nothing to install.
search_8k_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 search_8k_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 search_8k_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.
search_8k_filings is provided by the FilingFirehose MCP server (https://filingfirehose.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on FilingFirehose, and thousands of servers like it.
This server
Across the catalogue