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...
Part of the FilingFirehose server.
Free to start. No card required.
AI agents call search_8k_filings to retrieve information from FilingFirehose without modifying any data. This is common in research, monitoring, and reporting workflows where the agent needs context before taking action. Because read operations don't change state, they are generally safe to allow without restrictions -- but you may still want rate limits to control API costs.
Even though search_8k_filings only reads data, uncontrolled read access can leak sensitive information or rack up API costs. An agent caught in a retry loop could make thousands of calls per minute. A rate limit gives you a safety net without blocking legitimate use.
Read-only tools are safe to allow by default. No rate limit needed unless you want to control costs.
{
"version": "1",
"default": "deny",
"tools": {
"search_8k_filings": {}
}
}See the full FilingFirehose policy for all 4 tools.
These attack patterns abuse exactly the kind of access search_8k_filings gives an agent. Each links to the full case and the policy that stops it:
Other read tools across the catalogue. The same approach applies to each: allow, with a rate cap to control cost.
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.
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.
Deterministic rules across all 4 FilingFirehose tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
4,600+ MCP servers and 31,000+ tools scanned and risk-classified.