AI agents call get_volume_profile to retrieve information from TradingView MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Volume profile is a technical analysis metric that reads historical or real-time market data to show price levels by trading volume. This is a retrieval operation with no side effects. The empty description lowers confidence slightly, but the tool name and consistent pattern with other 'get_' indicator functions on the server strongly indicate a Read operation.
From the tool's definition Tool name 'get_volume_profile' indicates retrieval of trading/market data. Server description emphasizes 'real-time market data' and 'trading analysis'. Sibling tools (get_adx, get_atr, get_bollinger_bands) are all technical indicator retrieval functions.
Documented attack patterns abuse exactly the kind of access get_volume_profile gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and TradingView MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_volume_profile:
{
"version": "1",
"default": "deny",
"tools": {
"get_volume_profile": {}
}
}get_volume_profile 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.
get_volume_profile. It is categorised as a Read tool in the TradingView MCP Server MCP Server, which means it retrieves data without modifying state.
Register the TradingView MCP Server MCP server in PolicyLayer and add a rule for get_volume_profile: 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 Server. Nothing to install.
get_volume_profile 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 get_volume_profile 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 get_volume_profile. 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.
get_volume_profile is provided by the TradingView MCP Server MCP server (lev-corrupted/tradingviewmcpserver). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from TradingView MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
33 TradingView MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.