Take a screenshot of the TradingView chart
AI agents call capture_screenshot to retrieve information from TradingView MCP Bridge without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool captures and returns visual information about the current state of a TradingView chart. It is a read-only operation that retrieves data without side effects. No data is created, modified, deleted, or financial transactions are initiated. The screenshot is a passive observation of existing chart state, fitting the 'Read' category (retrieve or query data; no side effects).
From the tool's definition Tool name is 'capture_screenshot' with description 'Take a screenshot of the TradingView chart'. The action is purely retrieval of visual data with no modification, deletion, execution of code, or financial impact.
Documented attack patterns abuse exactly the kind of access capture_screenshot gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and TradingView MCP Bridge, and nothing reaches the server without passing your rules. This is the rule we recommend for capture_screenshot:
{
"version": "1",
"default": "deny",
"tools": {
"capture_screenshot": {}
}
}capture_screenshot is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Take a screenshot of the TradingView chart. It is categorised as a Read tool in the TradingView MCP Bridge MCP Server, which means it retrieves data without modifying state.
Register the TradingView MCP Bridge 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 Bridge. 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 Bridge MCP server (tradesdontlie/tradingview-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 78 TradingView MCP Bridge tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
78 TradingView MCP Bridge tools catalogued and risk-classified — across an index of 42,500+ MCP servers.