Take a screenshot of the TradingView chart
AI agents call capture_screenshot to retrieve information from TradingView MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool captures the current state of a TradingView chart interface for inspection purposes. It retrieves data (a visual representation) with no side effects on the chart data, indicators, alerts, or any system state. The operation is purely observational and non-destructive, fitting squarely within the Read category.
From the tool's definition Tool name 'capture_screenshot' and description 'Take a screenshot of the TradingView chart' describe a retrieval operation that reads the current visual state without modifying, deleting, or executing any operations.
Attacks that exploit this kind of access
Take a screenshot of the TradingView chart. It is categorised as a Read tool in the TradingView MCP MCP Server, which means it retrieves data without modifying state.
Register the TradingView MCP server in PolicyLayer and add a rule for capture_screenshot: 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.
capture_screenshot is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the capture_screenshot 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 capture_screenshot. 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.
capture_screenshot 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.
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 →