This tool is used to set the tokens for Zerodha. You will get the request token from the user (might be in a URL), then call another function to generate the access token, save both tokens to the config file, and return a success message if the tokens are set successfully.
AI agents use set-zerodha-tokens to create or update resources in Zerodha MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Zerodha MCP Server environment.
This tool writes authentication tokens (request token and access token) to a configuration file. It modifies stored credentials persistently, which is a Write operation. The severity is high because misuse could allow an attacker to hijack the Zerodha session by setting malicious tokens, potentially enabling unauthorized access to trading operations including financial transactions.
From the tool's definition set the tokens...save both tokens to the config file
Attacks that exploit this kind of access
This tool is used to set the tokens for Zerodha. You will get the request token from the user (might be in a URL), then call another function to generate the access token, save both tokens to the config file, and return a success message if the tokens are set successfully. It is categorised as a Write tool in the Zerodha MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Zerodha MCP Server MCP server in PolicyLayer and add a rule for set-zerodha-tokens: 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.
set-zerodha-tokens is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the set-zerodha-tokens 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 set-zerodha-tokens. 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.
set-zerodha-tokens is provided by the Zerodha MCP Server MCP server (maniklakhanpal/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 →