fund_history

Quarter-by-quarter filing history and a summary (turnover, concentration, favorites).

SERVERFolioFact SOURCEhttps://foliofact.com/mcp

Low RISK CLASS

Category Read

Parameters 11 required

Recommended Allowedsee the rule below

Registry record Grade C, identity unverified Pull the record →

This record as markdown: /tools/com-foliofact-foliofact/fund-history.md

WHAT IT DOES

What fund_history does on FolioFact

AI agents call fund_history to retrieve information from FolioFact 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
`slug`	string	Yes	Fund slug (URL identifier).

Parameters from the server's own tool schema.

RISK

Why fund_history is rated Low

Even though fund_history 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

RECOMMENDED RULE

The rule that runs fund_history safely

PolicyLayer is an MCP gateway: it sits between your AI agents and FolioFact, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For fund_history, this is the rule to start with:

fund_history Allowed

fund_history is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "fund_history": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect FolioFact, apply this rule, and every fund_history call is checked against it from then on.

FAQ

Questions about fund_history

What does the fund_history tool do? +

Quarter-by-quarter filing history and a summary (turnover, concentration, favorites). It is categorised as a Read tool in the FolioFact MCP Server, which means it retrieves data without modifying state.

What parameters does fund_history accept? +

fund_history accepts 1 parameter: slug. Required: slug. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on fund_history? +

Register the FolioFact MCP server in PolicyLayer and add a rule for fund_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 FolioFact. Nothing to install.

What risk level is fund_history? +

fund_history is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit fund_history? +

Yes. Add a rate_limit block to the fund_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.

How do I block fund_history completely? +

Set action: deny in the PolicyLayer policy for fund_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.

What MCP server provides fund_history? +

fund_history is provided by the FolioFact MCP server (https://foliofact.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on FolioFact, and thousands of servers like it.

This server

All 13 FolioFact tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →