searchSEC
Returns a list of SEC filing information (including the submission URL) corresponding to the given search parameters.
This record as markdown: /tools/com-api-ninjas-mcp/searchsec.md
What searchSEC does on API Ninjas
AI agents call searchSEC to retrieve information from API Ninjas 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 |
|---|---|---|---|
end | string | — | End date to search. Must be in YYYY-MM-DD format (e.g. 2023-04-01). |
limit | integer | — | Number of results to return from 1 to 100. By default, up to 2 results are returned. |
start | string | — | Start date to search. Must be in YYYY-MM-DD format (e.g. 2023-04-01). |
filing | string | Yes | SEC filing form type. |
ticker | string | Yes | Ticker symbol of the company to search (e.g. AAPL for Apple). |
Parameters from the server's own tool schema.
Why searchSEC is rated Low
Even though searchSEC only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.
Attacks that exploit this kind of access
The rule that runs searchSEC safely
PolicyLayer is an MCP gateway: it sits between your AI agents and API Ninjas, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For searchSEC, this is the rule to start with:
searchSEC 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 API Ninjas, apply this rule, and every searchSEC call is checked against it from then on.
Questions about searchSEC
Returns a list of SEC filing information (including the submission URL) corresponding to the given search parameters. It is categorised as a Read tool in the API Ninjas MCP Server, which means it retrieves data without modifying state.
searchSEC accepts 5 parameters: end, limit, start, filing, ticker. Required: filing, ticker. The full parameter table on this page comes from the server's own tool schema.
Register the API Ninjas MCP server in PolicyLayer and add a rule for searchSEC: 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 API Ninjas. Nothing to install.
searchSEC 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 searchSEC 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 searchSEC. 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.
searchSEC is provided by the API Ninjas MCP server (https://mcp.api-ninjas.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on API Ninjas, and thousands of servers like it.
This server
Across the catalogue