get_historical_candles

A read tool on the Groww MCP server.

SERVERGroww MCP Server SOURCEabhijeetmohanan/growwmcp
Low RISK CLASS
Category Read
Parameters 00 required
Recommended Allowedsee the rule below
Registry record Grade F, identity unverified Pull the record →

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…

Questions about get_historical_candles

What does the get_historical_candles tool do? +

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.

How do I enforce a policy on get_historical_candles? +

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.

What risk level is get_historical_candles? +

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

Can I rate-limit get_historical_candles? +

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.

How do I block get_historical_candles completely? +

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.

What MCP server provides get_historical_candles? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Groww MCP Server's. Pull the full record:

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.