mfapi.nav.history
Get historical Net Asset Value (NAV) records for an India mutual fund scheme, most recent first. Returns daily NAV values in Indian Rupees (INR) with dates. Some schemes have 20+ years of history. Useful for performance analysis, CAGR calculations, SIP return modelling, and trend visualization. L...
This record as markdown: /tools/io-github-whiteknightonhorse-apibase/mfapi.nav.history.md
What mfapi.nav.history does on Apibase
AI agents call mfapi.nav.history 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 historical NAV records to return, most recent first (1–1000, default 100) |
scheme_code | integer | Yes | AMFI scheme code (integer). Use mfapi.scheme_search to find the code for a fund. |
Parameters from the server's own tool schema.
Why mfapi.nav.history is rated Low
Retrieves historical financial data for analysis without modifying or executing transactions.
From the tool's definition Get historical Net Asset Value records, returns daily NAV values, no side effects
Attacks that exploit this kind of access
The rule that runs mfapi.nav.history 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.nav.history, this is the rule to start with:
mfapi.nav.history 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.nav.history call is checked against it from then on.
Questions about mfapi.nav.history
Get historical Net Asset Value (NAV) records for an India mutual fund scheme, most recent first. Returns daily NAV values in Indian Rupees (INR) with dates. Some schemes have 20+ years of history. Useful for performance analysis, CAGR calculations, SIP return modelling, and trend visualization. Limit parameter controls how many records are returned (default 100, max 1000). Use mfapi.schemes.search to find the scheme_code for a fund by name. 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.nav.history accepts 2 parameters: limit, scheme_code. Required: scheme_code. 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.nav.history: 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.nav.history 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.nav.history 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.nav.history. 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.nav.history 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