get_trade_history
AI agents call get_trade_history 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 historical trade data from a trading platform. It has no side effects—it queries and returns information without modifying, deleting, or executing external actions. This is a typical Read operation. The absence of a description lowers confidence from 0.90 to 0.85, but the explicit 'get_' prefix and context of a financial data access server make the Read category clear.
From the tool's definition Tool name is 'get_trade_history' which follows a read pattern (get_*). The DhanHQ server context indicates it provides access to 'trade history' among other data retrieval functions.
Attacks that exploit this kind of access
get_trade_history. 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_trade_history: 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_trade_history 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_trade_history 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_trade_history. 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_trade_history 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 →