Search real-time SEC filings (8-K, 10-K, 10-Q, S-1) for AI/autonomous operations mentions. Returns filings ranked by AI-relevance score with key extracted passages. Use this tool when: - A research agent needs to know what public companies are saying about AI in their official filings - An invest...
AI agents call get_sec_filings to retrieve information from Omni Service Node without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs read-only data retrieval from public SEC filings. It searches, ranks, and returns information without creating, modifying, deleting, or executing any operations. The use cases confirm passive research applications (identifying disclosures, monitoring regulatory filings, investor intelligence).
From the tool's definition Tool retrieves and searches real-time SEC filings (8-K, 10-K, 10-Q, S-1) and returns results ranked by relevance with extracted passages. Described actions are 'search' and 'returns' — query operations with no modification or deletion of data.
Attacks that exploit this kind of access
Search real-time SEC filings (8-K, 10-K, 10-Q, S-1) for AI/autonomous operations mentions. Returns filings ranked by AI-relevance score with key extracted passages. Use this tool when: - A research agent needs to know what public companies are saying about AI in their official filings - An investor agent is identifying companies making material AI investments or disclosures - You need to detect new AI risk factors companies are disclosing to regulators - A compliance agent is monitoring for AI-related regulatory disclosures Returns per filing: company, ticker, form_type, filed_date, ai_relevance_score (0-100), key_passages, ai_keywords_found, material_disclosure (YES/NO), filing_url. Example: getSecFilings({ query:. It is categorised as a Read tool in the Omni Service Node MCP Server, which means it retrieves data without modifying state.
Register the Omni Service Node MCP server in PolicyLayer and add a rule for get_sec_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 Omni Service Node. Nothing to install.
get_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 get_sec_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 get_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.
get_sec_filings is provided by the Omni Service Node MCP server (luckkyyy23/omni-service-node). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →