depth_get
Get order book / DOM (Depth of Market) data from the chart
This record as markdown: /tools/debarpan2000-tradingview-mcp/depth-get.md
What depth_get does on TradingView MCP Server
AI agents call depth_get to retrieve information from TradingView MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why depth_get is rated Low
This tool retrieves market data (order book depth information) from TradingView's chart interface. It performs a query operation without creating, modifying, deleting, or executing any trading actions. The operation is read-only and has no side effects on the system or market state.
From the tool's definition Tool name 'depth_get' and description 'Get order book / DOM (Depth of Market) data from the chart' indicate a retrieval operation with no modification of state.
Attacks that exploit this kind of access
The rule that runs depth_get safely
PolicyLayer is an MCP gateway: it sits between your AI agents and TradingView MCP Server, 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 is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect TradingView MCP Server, apply this rule, and every depth_get call is checked against it from then on.
Questions about depth_get
Get order book / DOM (Depth of Market) data from the chart. It is categorised as a Read tool in the TradingView MCP Server MCP Server, which means it retrieves data without modifying state.
Register the TradingView MCP Server 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 Server. 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 Server MCP server (debarpan2000/tradingview-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on TradingView MCP Server, and thousands of servers like it.
This server
Across the catalogue