depth_get

Get order book / DOM (Depth of Market) data from the chart

SERVERTradingView MCP Bridge SOURCEbyeung888/tradingview-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/byeung888-tradingview-mcp/depth-get.md

WHAT IT DOES

What depth_get does on TradingView MCP Bridge

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

RISK

Why depth_get is rated Low

This tool queries and returns market depth information from a chart display. It is a read-only operation that retrieves data without creating, modifying, deleting, or executing any actions. While the sibling tools include destructive operations (alert_delete) and potentially risky execute-class operations (batch_run, chart_manage_indicator), depth_get is purely informational.

From the tool's definition 'Get order book / DOM (Depth of Market) data from the chart' — the tool retrieves market data with no side effects or modifications to state.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs depth_get safely

PolicyLayer is an MCP gateway: it sits between your AI agents and TradingView MCP Bridge, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For depth_get, this is the rule to start with:

depth_get Allowed

depth_get is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "depth_get": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect TradingView MCP Bridge, apply this rule, and every depth_get call is checked against it from then on.

FAQ

Questions about depth_get

What does the depth_get tool do? +

Get order book / DOM (Depth of Market) data from the chart. It is categorised as a Read tool in the TradingView MCP Bridge MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on depth_get? +

Register the TradingView MCP Bridge MCP server in PolicyLayer and add a rule for depth_get: 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 TradingView MCP Bridge. Nothing to install.

What risk level is depth_get? +

depth_get is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit depth_get? +

Yes. Add a rate_limit block to the depth_get 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.

How do I block depth_get completely? +

Set action: deny in the PolicyLayer policy for depth_get. 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.

What MCP server provides depth_get? +

depth_get is provided by the TradingView MCP Bridge MCP server (byeung888/tradingview-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on TradingView MCP Bridge, and thousands of servers like it.

This server

All 78 TradingView MCP Bridge tools →

Across the catalogue

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →