Get order book / DOM (Depth of Market) data from the chart
AI agents call depth_get to retrieve information from TradingView MCP Bridge without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'get' prefix combined with the description of retrieving market depth information indicates this is a read-only operation. It queries existing chart data without modifying, executing commands, deleting, or committing financial transactions.
From the tool's definition Tool retrieves 'order book / DOM (Depth of Market) data from the chart' — a passive data query operation with no side effects, state changes, or external actions triggered.
Attacks that exploit this kind of access
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.
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.
depth_get is a Read tool with low risk. Read-only tools are generally safe to allow by default.
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.
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.
depth_get is provided by the TradingView MCP Bridge MCP server (thinhbv/tradingview_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →