get_historical_candles
A read tool on the Groww MCP server.
This record as markdown: /tools/abhijeetmohanan-growwmcp/get-historical-candles.md
What get_historical_candles does on Groww MCP Server
AI agents call get_historical_candles to retrieve information from Groww MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_historical_candles is rated Low
The tool retrieves historical market data (candles), which is a read-only operation with no side effects. Even within a financial trading platform context, querying historical price data poses minimal risk—it does not execute trades, move money, delete data, or trigger external operations. The main sibling tools are all getters/queries.
From the tool's definition Tool name 'get_historical_candles' indicates data retrieval of historical price data. No description provided, but naming convention and context among sibling tools (get_holdings, get_live_ltp, get_ltp, get_market_depth) which are all read-only data queries…
Attacks that exploit this kind of access
The rule that runs get_historical_candles safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Groww MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For get_historical_candles, this is the rule to start with:
get_historical_candles 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 Groww MCP Server, apply this rule, and every get_historical_candles call is checked against it from then on.
Questions about get_historical_candles
get_historical_candles is a read tool on the Groww MCP Server MCP server. It is categorised as a Read tool in the Groww MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Groww MCP Server MCP server in PolicyLayer and add a rule for get_historical_candles: 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 Groww MCP Server. Nothing to install.
get_historical_candles 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 get_historical_candles 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 get_historical_candles. 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.
get_historical_candles is provided by the Groww MCP Server MCP server (abhijeetmohanan/growwmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Groww MCP Server, and thousands of servers like it.
This server
Across the catalogue