draw_change_point · TradingView MCP: Risk & Policy

WHAT IT DOES

What draw_change_point does on TradingView MCP

AI agents use draw_change_point to create or update resources in TradingView MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your TradingView MCP environment.

WHY IT NEEDS A POLICY

Why draw_change_point needs a policy

This tool modifies an existing drawing object on a TradingView chart by repositioning one of its points. This is a reversible write/update operation — it changes chart state but does not delete data or execute code, and has no financial transaction implications. Misuse could corrupt chart analysis setups but is recoverable.

From the tool's definition Move a single point of a drawing by index... dragging one endpoint of a trend line or one handle of a pitchfork while leaving the others

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

draw_change_point Rate-limited

draw_change_point stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "draw_change_point": {
      "limits": [
        {
          "counter": "draw_change_point_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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 MCP, so you can run agents against it safely.

FAQ

Questions about draw_change_point

What does the draw_change_point tool do? +

Move a single point of a drawing by index (0-based). Useful for dragging one endpoint of a trend line or one handle of a pitchfork while leaving the others. It is categorised as a Write tool in the TradingView MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on draw_change_point? +

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

What risk level is draw_change_point? +

draw_change_point is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit draw_change_point? +

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

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

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