mfapi.schemes.list
Paginated list of all 37,000+ AMFI-registered India mutual fund schemes. Returns scheme codes, names, and ISIN identifiers for each page. Useful for bulk enumeration or building fund directories. Use mfapi.schemes.search for keyword-based lookup instead of iterating all pages. Data source: MFAPI ...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/mfapi.schemes.list.md
What mfapi.schemes.list does on Apibase
AI agents call mfapi.schemes.list 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 |
|---|---|---|---|
page | integer | — | Page number for pagination (default 1) |
per_page | integer | — | Number of schemes per page (1–200, default 50) |
Parameters from the server's own tool schema.
Why mfapi.schemes.list is rated Low
Retrieves publicly available mutual fund scheme metadata with no side effects or data modification.
From the tool's definition Paginated list of mutual fund schemes, returns codes, names, ISIN identifiers.
Attacks that exploit this kind of access
The rule that runs mfapi.schemes.list 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.list, this is the rule to start with:
mfapi.schemes.list 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.list call is checked against it from then on.
Questions about mfapi.schemes.list
Paginated list of all 37,000+ AMFI-registered India mutual fund schemes. Returns scheme codes, names, and ISIN identifiers for each page. Useful for bulk enumeration or building fund directories. Use mfapi.schemes.search for keyword-based lookup instead of iterating all pages. 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.list accepts 2 parameters: page, per_page. 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.list: 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.list 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.list 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.list. 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.list 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