indicator_toggle_visibility · Tradingview MCP: Risk & Policy

WHAT IT DOES

What indicator_toggle_visibility does on Tradingview

AI agents invoke indicator_toggle_visibility to trigger actions in Tradingview. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why indicator_toggle_visibility needs a policy

This tool executes an action in an external application (TradingView Desktop) by toggling the visibility of a chart indicator. It is not a simple data read or write operation; it drives browser/app automation that changes the visible state of the UI. While reversible (toggling back), it falls under Execute because it triggers an external operation via CDP.

From the tool's definition 'Show or hide an indicator/study on the chart' — triggers a UI state change in the TradingView Desktop app via Chrome DevTools Protocol

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

indicator_toggle_visibility Rate-limited

indicator_toggle_visibility stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "indicator_toggle_visibility": {
      "limits": [
        {
          "counter": "indicator_toggle_visibility_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Tradingview, so you can run agents against it safely.

FAQ

Questions about indicator_toggle_visibility

What does the indicator_toggle_visibility tool do? +

Show or hide an indicator/study on the chart. It is categorised as a Execute tool in the Tradingview MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on indicator_toggle_visibility? +

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

What risk level is indicator_toggle_visibility? +

indicator_toggle_visibility is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit indicator_toggle_visibility? +

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

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

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