Get the current user profile from Zerodha
AI agents call get_user_profile 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 retrieves user profile information from Zerodha without creating, modifying, deleting, or executing any operations. It is a read-only query operation. While it accesses personal financial account information (which could be sensitive), the tool itself performs no risky actions—severity is low because misuse would only expose data the authenticated user already has access to, not commit financial…
From the tool's definition Tool name 'get_user_profile' and description 'Get the current user profile from Zerodha' indicate data retrieval with no modification or side effects.
Attacks that exploit this kind of access
Get the current user profile from Zerodha. 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 get_user_profile: 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.
get_user_profile 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_user_profile 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_user_profile. 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_user_profile 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 →