Recent SEC 8-K material event filings for a ticker, with parsed item codes. Common codes: 1.02=contract terminated, 2.02=earnings release, 2.06=material impairment, 4.01=auditor changed, 4.02=non-reliance/restatement, 5.02=officer/director departure or appointment, 8.01=other. Filter by `itemCode...
Part of the Openinsider MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call recent_sec_filings to retrieve information from Openinsider 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 recent_sec_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.
tools:
recent_sec_filings:
rules:
- action: allowSee the full Openinsider policy for all 16 tools.
Agents calling read-class tools like recent_sec_filings have been implicated in these attack patterns. Read the full case and prevention policy for each:
Other tools in the Read risk category across the catalogue. The same policy patterns (rate-limit, allow) apply to each.
Recent SEC 8-K material event filings for a ticker, with parsed item codes. Common codes: 1.02=contract terminated, 2.02=earnings release, 2.06=material impairment, 4.01=auditor changed, 4.02=non-reliance/restatement, 5.02=officer/director departure or appointment, 8.01=other. Filter by `itemCodes`. Use when: - User asks 'what happened with TICKER' or 'why did TICKER move' - Investigating a price gap or unexpected catalyst - Looking specifically for restatements, impairments, or executive changes - Cross-referencing insider trades with the corporate event timeline.. It is categorised as a Read tool in the Openinsider MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for recent_sec_filings. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Openinsider MCP server.
recent_sec_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 recent_sec_filings rule in your Intercept 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 Intercept policy for recent_sec_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.
recent_sec_filings is provided by the Openinsider MCP server (openinsider-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.