populate_historicals
Populate historical financial data from discovered sources. This tool: - Checks NodeBench cache first (instant, free) - Falls back to SEC EDGAR if needed - Extracts revenue, EBITDA, margins, cash flows - Fills in the historical data section of the DCF model Requires: DCF model must be created fir...
This record as markdown: /tools/io-github-homenshum-nodebench/populate-historicals.md
What populate_historicals does on Nodebench
AI agents call populate_historicals to retrieve information from Nodebench without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why populate_historicals is rated Low
Even though populate_historicals 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 populate_historicals safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Nodebench, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For populate_historicals, this is the rule to start with:
populate_historicals 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 Nodebench, apply this rule, and every populate_historicals call is checked against it from then on.
Questions about populate_historicals
Populate historical financial data from discovered sources. This tool: - Checks NodeBench cache first (instant, free) - Falls back to SEC EDGAR if needed - Extracts revenue, EBITDA, margins, cash flows - Fills in the historical data section of the DCF model Requires: DCF model must be created first with create_dcf_model. It is categorised as a Read tool in the Nodebench MCP Server, which means it retrieves data without modifying state.
Register the Nodebench MCP server in PolicyLayer and add a rule for populate_historicals: 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 Nodebench. Nothing to install.
populate_historicals 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 populate_historicals 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 populate_historicals. 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.
populate_historicals is provided by the Nodebench MCP server (nodebench-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Nodebench, and thousands of servers like it.
This server
Across the catalogue