data_get_pine_tables
Read table data drawn by Pine Script indicators (table.new). Returns formatted text rows per table. Use study_filter to target a specific indicator.
This record as markdown: /tools/byeung888-tradingview-mcp/data-get-pine-tables.md
What data_get_pine_tables does on TradingView MCP Bridge
AI agents call data_get_pine_tables 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.
Why data_get_pine_tables is rated Low
This tool retrieves and queries data from Pine Script indicator tables—a classic read operation with no side effects. The data being read is already rendered on the chart and belongs to the user's own local TradingView instance. There is no risk of data deletion, modification, execution of arbitrary code, or financial impact.
From the tool's definition Tool description states "Read table data drawn by Pine Script indicators" and "Returns formatted text rows per table". The verb "Read" and "Returns" indicate retrieval without modification. No side effects or state changes are described.
Attacks that exploit this kind of access
The rule that runs data_get_pine_tables 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 data_get_pine_tables, this is the rule to start with:
data_get_pine_tables 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 Bridge, apply this rule, and every data_get_pine_tables call is checked against it from then on.
Questions about data_get_pine_tables
Read table data drawn by Pine Script indicators (table.new). Returns formatted text rows per table. Use study_filter to target a specific indicator. 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 data_get_pine_tables: 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.
data_get_pine_tables 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 data_get_pine_tables 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 data_get_pine_tables. 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.
data_get_pine_tables 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.
More on TradingView MCP Bridge, and thousands of servers like it.
This server
Across the catalogue