mfapi.schemes.search
Search across 37,000+ AMFI-registered India mutual fund schemes by name keyword. Returns matching scheme codes, names, and ISIN identifiers. Use the returned scheme_code to fetch current or historical NAV data. Supports partial matches — searching "HDFC" returns all HDFC schemes; "mid cap" return...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/mfapi.schemes.search.md
What mfapi.schemes.search does on Apibase
AI agents call mfapi.schemes.search to retrieve information from Apibase 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 |
|---|---|---|---|
limit | integer | — | Maximum number of results to return (1–100, default 20) |
query | string | Yes | Keyword to filter scheme names (e.g. "HDFC", "SBI Bluechip", "mid cap") |
Parameters from the server's own tool schema.
Why mfapi.schemes.search is rated Low
Retrieves financial scheme metadata without side effects, no account modifications or transactions possible.
From the tool's definition Search across 37,000+ AMFI-registered India mutual fund schemes by name keyword. Returns matching scheme codes, names, and ISIN identifiers.
Attacks that exploit this kind of access
The rule that runs mfapi.schemes.search safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Apibase, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For mfapi.schemes.search, this is the rule to start with:
mfapi.schemes.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 Apibase, apply this rule, and every mfapi.schemes.search call is checked against it from then on.
Questions about mfapi.schemes.search
Search across 37,000+ AMFI-registered India mutual fund schemes by name keyword. Returns matching scheme codes, names, and ISIN identifiers. Use the returned scheme_code to fetch current or historical NAV data. Supports partial matches — searching "HDFC" returns all HDFC schemes; "mid cap" returns all mid-cap funds. Data source: MFAPI (api.mfapi.in), MIT license, no authentication required. It is categorised as a Read tool in the Apibase MCP Server, which means it retrieves data without modifying state.
mfapi.schemes.search accepts 2 parameters: limit, query. Required: query. The full parameter table on this page comes from the server's own tool schema.
Register the Apibase MCP server in PolicyLayer and add a rule for mfapi.schemes.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 Apibase. Nothing to install.
mfapi.schemes.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 mfapi.schemes.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 mfapi.schemes.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.
mfapi.schemes.search is provided by the Apibase MCP server (apibase-mcp-client). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Apibase, and thousands of servers like it.
This server
Across the catalogue