AI agents use place_order to commit financial operations through Zerodha — usually the final step of a payment, billing, or trading workflow. A call moves real money.
Despite an empty description, the tool name 'place_order' combined with the server context — a Zerodha brokerage integration explicitly described as supporting order placement — makes it highly evident this tool places financial trading orders. This commits real financial obligations and can result in significant monetary loss if misused, warranting a Financial/critical classification.
From the tool's definition Tool name 'place_order' on a Zerodha trading account MCP server described as enabling 'placing orders' for trading accounts.
Documented attack patterns abuse exactly the kind of access place_order 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 place_order:
{
"version": "1",
"default": "deny",
"tools": {
"place_order": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
}
} Any call to place_order is blocked until a human approves it. The rest of the server keeps working.
Free to start. No card required.
place_order. It is categorised as a Financial tool in the Zerodha MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Zerodha MCP server in PolicyLayer and add a rule for place_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 Zerodha. Nothing to install.
place_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_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_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_order 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.