AI agents use place_zerodha_sell_order to commit financial operations through Trade-MCP — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool directly executes sell orders through a financial broker (Zerodha), committing real financial transactions. Misuse by an AI agent could result in unauthorized liquidation of holdings, significant financial losses, and irreversible market transactions. Financial category is the most severe applicable, and the blast radius is critical given real money and securities are involved.
From the tool's definition 'Places an order using the Zerodha Broker' combined with tool name 'place_zerodha_sell_order' and server context 'trading automation...place buy/sell orders'
Attacks that exploit this kind of access
Places an order using the Zerodha Broker. It is categorised as a Financial tool in the Trade-MCP MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Trade- MCP server in PolicyLayer and add a rule for place_zerodha_sell_order: 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 Trade-MCP. Nothing to install.
place_zerodha_sell_order is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the place_zerodha_sell_order 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 place_zerodha_sell_order. 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.
place_zerodha_sell_order is provided by the Trade- MCP server (samarjyoti496/trade-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 →