Reanuda el sistema después de una pausa.
AI agents invoke trader_resume 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.
This tool resumes a paused system/workflow, which constitutes triggering an external operation. Given the trading/financial context (TradingView with automation capabilities including alerts and chart management), resuming automation could trigger trades or alerts, but the tool itself is an execution control action rather than a direct financial transaction.
From the tool's definition 'Reanuda el sistema después de una pausa' (Resumes the system after a pause) — triggers an external operational state change in the TradingView Desktop app via Chrome DevTools Protocol
Attacks that exploit this kind of access
Reanuda el sistema después de una pausa. 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.
Register the Tradingview MCP server in PolicyLayer and add a rule for trader_resume: 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.
trader_resume is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the trader_resume 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 trader_resume. 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.
trader_resume 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.
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 →