Low Risk

chart_get_state

Get current chart state (symbol, timeframe, chart type, indicators)

How to control chart_get_state ↓

AI agents call chart_get_state 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.

Low Risk

This tool queries and retrieves the current state of a TradingView chart without modifying, executing, or destructively affecting any data or system state. It is a pure read operation suitable for chart analysis workflows.

From the tool's definition Tool name 'chart_get_state' and description 'Get current chart state' indicate a retrieval operation with no side effects. Returns read-only information about symbol, timeframe, chart type, and indicators.

Documented attack patterns abuse exactly the kind of access chart_get_state gives an agent:

PolicyLayer is an MCP gateway — it sits between your AI agents and TradingView MCP Bridge, and nothing reaches the server without passing your rules. This is the rule we recommend for chart_get_state:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "chart_get_state": {}
  }
}

chart_get_state is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register TradingView MCP Bridge — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the chart_get_state tool do? +

Get current chart state (symbol, timeframe, chart type, indicators). 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 chart_get_state? +

Register the TradingView MCP Bridge MCP server in PolicyLayer and add a rule for chart_get_state: 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 chart_get_state? +

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

Can I rate-limit chart_get_state? +

Yes. Add a rate_limit block to the chart_get_state 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 chart_get_state completely? +

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

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

Enforce policy on every TradingView MCP Bridge tool call.

Deterministic rules across all 78 TradingView MCP Bridge tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

Free to start. No card required.

78 TradingView MCP Bridge tools catalogued and risk-classified — across an index of 42,500+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.