edgar_full_text_search
Full-text search across all SEC filings via the EDGAR EFTS index. Filter by comma-separated form types and date range. Useful for finding filings that mention specific terms.
This record as markdown: /tools/io-github-blackboxfoundry-livedatalink/edgar-full-text-search.md
What edgar_full_text_search does on Livedatalink
AI agents call edgar_full_text_search to retrieve information from Livedatalink 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 |
|---|---|---|---|
forms | string | — | Comma-separated form types to filter (e.g. '10-K,10-Q'). Optional. |
limit | number | — | Maximum rows to return (default 25, max 100). |
query | string | Yes | Search query (e.g. 'cybersecurity incident', 'going concern'). |
end_date | string | — | Optional ISO date upper bound (YYYY-MM-DD). |
start_date | string | — | Optional ISO date lower bound (YYYY-MM-DD). |
Parameters from the server's own tool schema.
Why edgar_full_text_search is rated Low
This tool retrieves and searches publicly available SEC filing data without side effects. It is a standard search/query function that returns results without modifying data, executing commands, or creating financial transactions. The low severity reflects that misuse would at worst retrieve sensitive-but-public corporate information, with no destructive or financial impact.
From the tool's definition Tool performs 'full-text search' across SEC filings with filtering capabilities. The description explicitly states it is 'useful for finding filings that mention specific terms' — a pure retrieval and query operation with no modification, deletion, or…
Attacks that exploit this kind of access
The rule that runs edgar_full_text_search safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Livedatalink, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For edgar_full_text_search, this is the rule to start with:
edgar_full_text_search 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 Livedatalink, apply this rule, and every edgar_full_text_search call is checked against it from then on.
Questions about edgar_full_text_search
Full-text search across all SEC filings via the EDGAR EFTS index. Filter by comma-separated form types and date range. Useful for finding filings that mention specific terms. It is categorised as a Read tool in the Livedatalink MCP Server, which means it retrieves data without modifying state.
edgar_full_text_search accepts 5 parameters: forms, limit, query, end_date, start_date. Required: query. The full parameter table on this page comes from the server's own tool schema.
Register the Livedatalink MCP server in PolicyLayer and add a rule for edgar_full_text_search: 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 Livedatalink. Nothing to install.
edgar_full_text_search 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 edgar_full_text_search 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 edgar_full_text_search. 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.
edgar_full_text_search is provided by the Livedatalink MCP server (https://livedatalink.ai/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Livedatalink, and thousands of servers like it.
This server
Across the catalogue