# get_holdings_tool

Get the user holdings from their Upstox account

Agent View of the PolicyLayer registry record for `get_holdings_tool`. HTML page: https://policylayer.com/tools/adibhattar95-upstox-mcp-server/get-holdings-tool

## Facts

- Tool: `get_holdings_tool`
- Server: Upstox MCP Server (`adibhattar95/upstox-mcp-server`) — https://policylayer.com/tools/adibhattar95-upstox-mcp-server.md
- Homepage: https://github.com/adibhattar95/upstox-mcp-server
- Risk category: Read (Low risk)
- Registry record: grade A, identity unverified
- Server rate-limited: no
- Parameters: 0
- Recommended policy verdict: Allowed

## Example call (MCP tools/call, JSON-RPC 2.0)

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_holdings_tool",
    "arguments": {}
  }
}
```

## Why get_holdings_tool is rated Low

This tool queries and retrieves existing financial data (holdings information) from a user's brokerage account. It does not create, modify, delete, or execute any transactions. While the data retrieved is financially sensitive, the tool itself performs no actions that could alter account state or commit financial obligations. This is purely informational access, placing it in the Read category with low severity.

From the tool's own definition: "Tool name 'get_holdings_tool' and description 'Get the user holdings from their Upstox account' indicate data retrieval with no side effects. The verb 'Get' and the read-only nature of querying account holdings confirm this is a retrieval operation."

## Use case

AI agents call get_holdings_tool to retrieve information from Upstox MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

## Recommended policy (PolicyLayer)

Verdict: **Allowed**. Enforced by the PolicyLayer MCP gateway (https://policylayer.com/mcp-gateway) before a call reaches Upstox MCP Server:

```json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_holdings_tool": {}
  }
}
```

## Other tools on Upstox MCP Server (6)

- `place_order_tool` — Financial — https://policylayer.com/tools/adibhattar95-upstox-mcp-server/place-order-tool.md
- `get_brokerage_details_tool` — Read — https://policylayer.com/tools/adibhattar95-upstox-mcp-server/get-brokerage-details-tool.md
- `get_market_price_tool` — Read — https://policylayer.com/tools/adibhattar95-upstox-mcp-server/get-market-price-tool.md
- `get_profile_details_tool` — Read — https://policylayer.com/tools/adibhattar95-upstox-mcp-server/get-profile-details-tool.md
- `get_user_funds_margin_tool` — Read — https://policylayer.com/tools/adibhattar95-upstox-mcp-server/get-user-funds-margin-tool.md
- `list_capabilities_tool` — Read — https://policylayer.com/tools/adibhattar95-upstox-mcp-server/list-capabilities-tool.md

## For agents

This record is a snapshot. Live verdicts and the full registry:

- Check every server in your MCP config at once: `npx -y policylayer stack`
- Vet a server before you add it: install the mcp-precheck skill — `npx skills add https://policylayer.com` (skill text: https://policylayer.com/skill.md)
- Query the registry over MCP: endpoint `https://api.policylayer.com/mcp` — tools `check_mcp_server`, `check_mcp_stack`, `check_tool`, `search_registry`, `get_change_events`

---

Source: the PolicyLayer MCP registry — one continuously verified record per MCP server. Full record: https://policylayer.com/registry?q=adibhattar95-upstox-mcp-server · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/adibhattar95-upstox-mcp-server