// SCAN REPORT

Zerodha

12 tools. 3 can modify or destroy data without limits.

3 destructive tools with no built-in limits. Policy required.

Last updated: 11 Jun 2026

3 can modify or destroy data

9 read-only

12 tools total

Community server · catalogue entry verified 11/06/2026

How to control Zerodha ↓

TOOL MAP

What Zerodha exposes to your agents

Read (9) Write / Execute (0) Destructive / Financial (3)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

Critical Risk

The most dangerous Zerodha tools

Financial · Critical modify_order On a trading/brokerage platform like Zerodha, modifying an order changes active financial transactions (price, quantity, order type) which directly affects financial commitments. Financial · Critical place_order 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 f Destructive · High cancel_order Cancelling an order is an irreversible action in the context of trading — once a market or limit order is cancelled, the trading opportunity is lost and the action cannot be undone.

3 of Zerodha's 12 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Zerodha

PolicyLayer is an MCP gateway — it sits between your AI agents and Zerodha, and nothing reaches the server without passing your rules. These are the rules we recommend:

Block financial tools by default

{
  "place_order": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Requires human approval."
      }
    ]
  }
}

Financial tools should be explicitly enabled per use case, not open by default.

Deny destructive operations

{
  "cancel_order": {
    "deny_if": [
      {
        "conditions": [],
        "on_deny": "Blocked by default. Requires approval."
      }
    ]
  }
}

Destructive tools should never be available to autonomous agents without human approval.

Cap read operations

{
  "get_access_token": {
    "limits": [
      {
        "counter": "get_access_token_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Zerodha — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON ZERODHA →

Free to start. No card required.

FULL CATALOGUE

All 12 Zerodha tools

FINANCIAL 2 tools

Financial place_order place_order Financial modify_order modify_order

DESTRUCTIVE 1 tools

Destructive cancel_order Cancel an order.

READ 9 tools

Read get_access_token Get the access token for the user. Read get_holdings get_holdings Read get_login_url Get the login URL for the user. Use this to get the login URL for the user and then redirect the user to the l Read get_margins get_margins Read get_order_history get_order_history Read get_order_trades get_order_trades Read get_orders get_orders Read get_positions get_positions Read get_user_profile get_user_profile

EXPLORE

Related servers

Other MCP servers with similar tools — same risk classification, starter policies for each.

FAQ

Questions about Zerodha

Can an AI agent move money through the Zerodha MCP server? +

Yes. The Zerodha server exposes 2 financial tools including place_order, modify_order. Without a policy, an autonomous agent can call these with no spend caps, no rate limits, and no approval flow. PolicyLayer lets you block financial tools by default, require human approval, or set per-tool rate limits — enforced on every call.

Can an AI agent delete data through the Zerodha MCP server? +

Yes. The Zerodha server exposes 1 destructive tools including cancel_order. These permanently remove resources with no undo. PolicyLayer blocks destructive tools by default so they never reach the upstream server.

How many tools does the Zerodha MCP server expose? +

12 tools across 3 categories: Destructive, Read, Write. 9 are read-only. 3 can modify, create, or delete data.

How do I enforce a policy on Zerodha? +

Register the Zerodha MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Zerodha tool call.

Deterministic rules across all 12 Zerodha tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON ZERODHA →

Free to start. No card required.

12 Zerodha tools catalogued and risk-classified — across an index of 43,000+ MCP servers.