rating_filter
AI agents call rating_filter to retrieve information from Tradingview without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Without a description, confidence is moderate. The name suggests filtering operations on ratings (likely sentiment, technical ratings, or user ratings), which is a read operation. The trading context and sibling tools being predominantly analytical support this interpretation. No evidence of side effects, financial transactions, or destructive operations.
From the tool's definition Tool named 'rating_filter' with no description provided. Given the context of a trading toolkit with sibling tools focused on analysis (backtest_strategy, coin_analysis, combined_analysis, bollinger_scan, etc.), 'rating_filter' most likely filters or…
Attacks that exploit this kind of access
rating_filter. It is categorised as a Read tool in the Tradingview MCP Server, which means it retrieves data without modifying state.
Register the Tradingview MCP server in PolicyLayer and add a rule for rating_filter: 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.
rating_filter 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 rating_filter 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 rating_filter. 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.
rating_filter is provided by the Tradingview MCP server (mrxjeus-cpu/trading-mcp-bot). 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 →