Get recent SEC filings from a real-time feed (48-hour window). Without filters, returns a summary of filing activity with notable highlights. With filters (form type, company), returns individual filings. Best for monitoring what's happening right now.
Part of the SEC Intelligence MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.
AI agents call get_live_filings to retrieve information from SEC Intelligence 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 get_live_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:
get_live_filings:
rules:
- action: allowSee the full SEC Intelligence policy for all 9 tools.
Agents calling read-class tools like get_live_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.
Get recent SEC filings from a real-time feed (48-hour window). Without filters, returns a summary of filing activity with notable highlights. With filters (form type, company), returns individual filings. Best for monitoring what's happening right now.. It is categorised as a Read tool in the SEC Intelligence MCP Server, which means it retrieves data without modifying state.
Add a rule in your Intercept YAML policy under the tools section for get_live_filings. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the SEC Intelligence MCP server.
get_live_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 get_live_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 get_live_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.
get_live_filings is provided by the SEC Intelligence MCP server (edgartools/sec-intelligence). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Open source. One binary. Zero dependencies.
npx -y @policylayer/intercept