get_historical_data

Retrieve historical OHLCV (Open, High, Low, Close, Volume) price data for a stock or cryptocurrency. Supports various time intervals from 1 minute to 1 month. Useful for charting and technical analysis.

Server Mcp Financex xerktech/mcp-financex
Category Read
Risk class Low
Parameters 00 required

What get_historical_data does on Mcp Financex

AI agents call get_historical_data to retrieve information from Mcp Financex without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why get_historical_data needs a policy

This tool queries and returns historical market data without creating, modifying, deleting, or executing any operations. It is a standard read operation used for charting and technical analysis. Although the server provides financial data, this particular tool does not move money, commit financial obligations, or trigger trades—it only retrieves public historical pricing information.

From the tool's definition Tool description states 'Retrieve historical OHLCV (Open, High, Low, Close, Volume) price data' — a pure data retrieval operation with no modification, deletion, or execution of external operations. No side effects mentioned.

Questions about get_historical_data

What does the get_historical_data tool do? +

Retrieve historical OHLCV (Open, High, Low, Close, Volume) price data for a stock or cryptocurrency. Supports various time intervals from 1 minute to 1 month. Useful for charting and technical analysis. It is categorised as a Read tool in the Mcp Financex MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_historical_data? +

Register the Mcp Financex MCP server in PolicyLayer and add a rule for get_historical_data: 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 Mcp Financex. Nothing to install.

What risk level is get_historical_data? +

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

Can I rate-limit get_historical_data? +

Yes. Add a rate_limit block to the get_historical_data 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 get_historical_data completely? +

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

get_historical_data is provided by the Mcp Financex MCP server (xerktech/mcp-financex). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.