Solicita el cierre de la posición abierta.
AI agents use trader_close_position to commit financial operations through Tradingview — usually the final step of a payment, billing, or trading workflow. A call moves real money.
Closing an open trading position is a financial action that irreversibly affects real or paper money positions in the market. Misuse by an AI agent could result in unintended liquidation of financial holdings, making this a critical financial risk.
From the tool's definition 'Solicita el cierre de la posición abierta' (Requests closing the open position) — directly closes a financial trading position
Attacks that exploit this kind of access
Solicita el cierre de la posición abierta. It is categorised as a Financial tool in the Tradingview MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Tradingview MCP server in PolicyLayer and add a rule for trader_close_position: 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_close_position is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the trader_close_position 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_close_position. 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_close_position 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 →