AI agents call get_positions 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.
The tool is a 'get_*' operation that queries the current state of a user's trading positions. This is a Read operation (retrieves data with no side effects). Severity is medium rather than low because the exposed data includes sensitive financial information (live position details, holdings, P&L exposure) that could be misused for fraud, market manipulation, or social engineering if disclosed to unauthorized…
From the tool's definition Tool named 'get_positions' with no description provided; in context of a trading/brokerage server (Zerodha), 'get_positions' semantically retrieves current open trading positions without modifying state.
Documented attack patterns abuse exactly the kind of access get_positions 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_positions:
{
"version": "1",
"default": "deny",
"tools": {
"get_positions": {}
}
}get_positions 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_positions. 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_positions: 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_positions 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_positions 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_positions. 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_positions 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.