AI agents call get_order_history to retrieve information from Zerodha without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves trading history information from a financial account, which is a read-only operation with no side effects. However, severity is elevated to 'medium' rather than 'low' because the exposed data concerns financial accounts and trading history, which could enable reconnaissance for fraud or unauthorized access patterns if misused by an unintended agent.
From the tool's definition Tool name 'get_order_history' and its position among sibling tools (get_holdings, get_positions, get_orders, get_user_profile) that are all data retrieval operations.
Documented attack patterns abuse exactly the kind of access get_order_history gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Zerodha, and nothing reaches the server without passing your rules. This is the rule we recommend for get_order_history:
{
"version": "1",
"default": "deny",
"tools": {
"get_order_history": {}
}
}get_order_history is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
get_order_history. It is categorised as a Read tool in the Zerodha MCP Server, which means it retrieves data without modifying state.
Register the Zerodha 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. 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 (mtwn105/zerodha-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Zerodha, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
12 Zerodha tools catalogued and risk-classified — across an index of 43,000+ MCP servers.