Validate if the current access token is still valid
AI agents call validate_token to retrieve information from Zerodha Trading Bot - MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a passive validation check without creating, modifying, deleting, executing commands, or committing financial transactions. It merely verifies whether an existing token remains valid, making it a Read category tool.
From the tool's definition The tool 'validate_token' checks the validity of an access token by querying authentication status with no side effects or data modifications. It is a read operation that retrieves authentication state information.
Attacks that exploit this kind of access
Validate if the current access token is still valid. It is categorised as a Read tool in the Zerodha Trading Bot - MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Zerodha Trading Bot - MCP Server MCP server in PolicyLayer and add a rule for validate_token: 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 Trading Bot - MCP Server. Nothing to install.
validate_token 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 validate_token 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 validate_token. 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.
validate_token is provided by the Zerodha Trading Bot - MCP Server MCP server (ssonthal/zerodhatradingbot-mcpserver). 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 →