AI agents call get_user_profile 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.
This tool retrieves user profile data from a Zerodha account. Retrieval operations that do not modify, delete, or execute code are classified as Read. The empty description reduces confidence slightly, but the clear read-only naming pattern and integration with other account-query tools (get_holdings, get_positions, get_margins) on the same server supports classification as Read with low severity, since exposure of…
From the tool's definition Tool name 'get_user_profile' indicates a retrieval operation with no side effects. Description is empty, but the function name and context (user profile retrieval on a trading platform) suggest it queries account information without modification.
Documented attack patterns abuse exactly the kind of access get_user_profile 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_user_profile:
{
"version": "1",
"default": "deny",
"tools": {
"get_user_profile": {}
}
}get_user_profile 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_user_profile. 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_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. 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 (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.