get_user_profile
AI agents call get_user_profile to retrieve information from Zerodha MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool follows a 'get_*' naming convention typical of Read operations. Despite empty description, the context of a trading platform server where other 'get_' prefixed tools retrieve account data without side effects strongly indicates this retrieves user profile information. No evidence suggests modification, deletion, or financial transactions. Confidence is reduced from 0.9 to 0.85 due to missing description.
From the tool's definition Tool name 'get_user_profile' indicates data retrieval. No description provided, but sibling tools on this Zerodha trading server include get_holdings, get_positions, get_margins, get_orders—all Read operations.
Attacks that exploit this kind of access
get_user_profile. It is categorised as a Read tool in the Zerodha MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Zerodha 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 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 MCP Server MCP server (jainsourabh2/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 →