Change indicator/study input values (e.g., length, source, period)
AI agents use indicator_set_inputs to create or update resources in TradingView MCP Jackson — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your TradingView MCP Jackson environment.
This tool modifies the configuration of an existing indicator by updating its input parameters. It is a reversible write operation—inputs can be changed back—with no code execution, data deletion, or financial transactions involved. Misuse could disrupt chart analysis setups but poses no irreversible harm.
From the tool's definition Change indicator/study input values (e.g., length, source, period)
Attacks that exploit this kind of access
Change indicator/study input values (e.g., length, source, period). It is categorised as a Write tool in the TradingView MCP Jackson MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the TradingView MCP Jackson 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 MCP Jackson. Nothing to install.
indicator_set_inputs is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
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.
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.
indicator_set_inputs is provided by the TradingView MCP Jackson MCP server (nimit791/tradingview-mcp-jackson). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →