searchETFs
Search for ETFs by name, AUM, expense ratio, holdings, or country. Results are sorted by AUM descending and paginated 50 per page. At least one filter parameter is required. Available to Business, Professional, or annual subscribers only.
This record as markdown: /tools/com-api-ninjas-mcp/searchetfs.md
What searchETFs does on API Ninjas
AI agents call searchETFs 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 |
|---|---|---|---|
name | string | — | Fund name to search for (e.g. vanguard 500 matches Vanguard S&P 500 ETF). Case-insensitive. Each word must match the start of a word in the fund name, in any or |
offset | integer | — | Number of results to skip for pagination. Page size is 50. |
country | string | — | Filter by ISO listing-country code -- the exchange the ETF trades on (e.g. US, GB, JP), not the fund's domicile. |
max_aum | number | — | Maximum assets under management in USD. |
min_aum | number | — | Minimum assets under management in USD. |
holdings | string | — | Comma-separated list of ticker symbols. Only ETFs that hold every listed ticker will be returned (AND match). Example: AAPL,MSFT. |
max_expense_ratio | number | — | Maximum annual expense ratio as a percentage. |
min_expense_ratio | number | — | Minimum annual expense ratio as a percentage (e.g. 0.1 for 0.1%). |
Parameters from the server's own tool schema.
Why searchETFs is rated Low
Even though searchETFs 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 searchETFs 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 searchETFs, this is the rule to start with:
searchETFs 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 searchETFs call is checked against it from then on.
Questions about searchETFs
Search for ETFs by name, AUM, expense ratio, holdings, or country. Results are sorted by AUM descending and paginated 50 per page. At least one filter parameter is required. Available to Business, Professional, or annual subscribers only. It is categorised as a Read tool in the API Ninjas MCP Server, which means it retrieves data without modifying state.
searchETFs accepts 8 parameters: name, offset, country, max_aum, min_aum, holdings, max_expense_ratio, min_expense_ratio. 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 searchETFs: 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.
searchETFs 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 searchETFs 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 searchETFs. 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.
searchETFs 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