# single_depth

A read tool on the Itick MCP server.

Agent View of the PolicyLayer registry record for `single_depth`. HTML page: https://policylayer.com/tools/281287994w-art-itick-mcp-server/single-depth

## Facts

- Tool: `single_depth`
- Server: Itick (`281287994w-art/itick-mcp-server`) — https://policylayer.com/tools/281287994w-art-itick-mcp-server.md
- Homepage: https://github.com/281287994w-art/itick-mcp-server
- Risk category: Read (Low risk)
- Registry record: grade B, 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": "single_depth",
    "arguments": {}
  }
}
```

## Why single_depth is rated Low

This tool retrieves market depth data (order book information) for a single security. Depth data is a read-only query of market state with no side effects, consistent with the server's stated purpose of exposing market data endpoints. The empty description lowers confidence slightly, but the naming pattern and server context strongly indicate a read operation.

From the tool's own definition: "Tool name 'single_depth' and sibling tools (batch_depths, batch_klines, batch_quotes, batch_ticks) are all data retrieval patterns. Server description states it 'provides market data' including 'depth'."

## Use case

AI agents call single_depth to retrieve information from Itick 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 Itick:

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

## Other tools on Itick (12)

- `batch_depths` — Read — https://policylayer.com/tools/281287994w-art-itick-mcp-server/batch-depths.md
- `batch_klines` — Read — https://policylayer.com/tools/281287994w-art-itick-mcp-server/batch-klines.md
- `batch_quotes` — Read — https://policylayer.com/tools/281287994w-art-itick-mcp-server/batch-quotes.md
- `batch_ticks` — Read — https://policylayer.com/tools/281287994w-art-itick-mcp-server/batch-ticks.md
- `single_kline` — Read — https://policylayer.com/tools/281287994w-art-itick-mcp-server/single-kline.md
- `single_quote` — Read — https://policylayer.com/tools/281287994w-art-itick-mcp-server/single-quote.md
- `single_tick` — Read — https://policylayer.com/tools/281287994w-art-itick-mcp-server/single-tick.md
- `stockInfo` — Read — https://policylayer.com/tools/281287994w-art-itick-mcp-server/stockinfo.md
- `stockIpo` — Read — https://policylayer.com/tools/281287994w-art-itick-mcp-server/stockipo.md
- `stockSplit` — Read — https://policylayer.com/tools/281287994w-art-itick-mcp-server/stocksplit.md
- `symbolHolidays` — Read — https://policylayer.com/tools/281287994w-art-itick-mcp-server/symbolholidays.md
- `symbolList` — Read — https://policylayer.com/tools/281287994w-art-itick-mcp-server/symbollist.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=281287994w-art-itick-mcp-server · API: https://policylayer.com/registry/api · Policy library: https://policylayer.com/policies/281287994w-art-itick-mcp-server