indicator_set_inputs · Tradingview MCP: Risk & Policy

WHAT IT DOES

What indicator_set_inputs does on Tradingview

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

WHY IT NEEDS A POLICY

Why indicator_set_inputs needs a policy

This tool modifies indicator settings reversibly without deleting data or executing arbitrary code. While it changes chart state and could affect analysis results if misconfigured, the changes are non-destructive and can be undone by resetting values. The blast radius is medium because incorrect inputs could mislead trading decisions, but the action itself is a standard Write operation on configuration data.

From the tool's definition Tool name 'indicator_set_inputs' and description 'Change indicator/study input values (e.g., length, source, period)' indicate modification of existing indicator configuration parameters.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

indicator_set_inputs Rate-limited

indicator_set_inputs 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": {
    "indicator_set_inputs": {
      "limits": [
        {
          "counter": "indicator_set_inputs_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, so you can run agents against it safely.

FAQ

Questions about indicator_set_inputs

What does the indicator_set_inputs tool do? +

Change indicator/study input values (e.g., length, source, period). It is categorised as a Write tool in the Tradingview MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on indicator_set_inputs? +

Register the Tradingview MCP server in PolicyLayer and add a rule for indicator_set_inputs: 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_set_inputs? +

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

Can I rate-limit indicator_set_inputs? +

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

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

indicator_set_inputs 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.