Fetch holdings summary via DhanHQ SDK.
AI agents call get_holdings_summary to retrieve information from DhanHQ 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 financial holdings data from a trading platform. While it is a Read operation (no modifications or deletions), the severity is elevated to medium because the data exposed includes sensitive financial information (portfolio holdings, asset positions, valuations) that could enable account reconnaissance, phishing, or social engineering attacks if accessed by an unauthorized agent.
From the tool's definition Tool name is 'get_holdings_summary' and description states 'Fetch holdings summary via DhanHQ SDK' — a retrieval operation with no side effects.
Attacks that exploit this kind of access
Fetch holdings summary via DhanHQ SDK. It is categorised as a Read tool in the DhanHQ MCP Server MCP Server, which means it retrieves data without modifying state.
Register the DhanHQ MCP Server MCP server in PolicyLayer and add a rule for get_holdings_summary: 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 DhanHQ MCP Server. Nothing to install.
get_holdings_summary 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_holdings_summary 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_holdings_summary. 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_holdings_summary is provided by the DhanHQ MCP Server MCP server (vedhasagaran/dhan-mcp-py). 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 →