Fibonacci retracement analysis for EGX stocks.
AI agents call egx_fibonacci_retracement 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.
This tool retrieves and analyzes market data (EGX stock prices) using the Fibonacci retracement mathematical method to identify potential support/resistance levels. It is purely analytical and returns calculated insights without side effects. The misuse risk is minimal—incorrect analysis may lead to poor trading decisions, but the tool itself cannot execute trades, move money, or modify any system state.
From the tool's definition Tool performs 'Fibonacci retracement analysis' which is a technical analysis calculation on historical market data. No modifications to data, no execution of trades, no financial transactions, and no destructive operations.
Attacks that exploit this kind of access
Fibonacci retracement analysis for EGX stocks. 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 egx_fibonacci_retracement: 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.
egx_fibonacci_retracement 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 egx_fibonacci_retracement 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 egx_fibonacci_retracement. 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.
egx_fibonacci_retracement 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 →