get_order_history
AI agents call get_order_history to retrieve information from Zerodha MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves historical order records without modifying data. While the description is empty (lowering confidence slightly), the name pattern and presence among other read-only tools (get_*) strongly suggests this is a data retrieval operation with no side effects. Access to historical trading data poses minimal risk compared to order modification or financial execution tools on this server.
From the tool's definition Tool name 'get_order_history' indicates a retrieval operation. No description provided, but naming convention and context among sibling tools (get_holdings, get_positions, get_margins, get_orders) suggest querying historical trading data.
Attacks that exploit this kind of access
get_order_history. It is categorised as a Read tool in the Zerodha MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Zerodha MCP Server MCP server in PolicyLayer and add a rule for get_order_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 Zerodha MCP Server. Nothing to install.
get_order_history 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_order_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.
Set action: deny in the PolicyLayer policy for get_order_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.
get_order_history is provided by the Zerodha MCP Server MCP server (jainsourabh2/zerodha-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the 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 →