Generate a full trade plan for a specific EGX stock.
AI agents use egx_trade_plan to create or update resources in Tradingview — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Tradingview environment.
An AI agent can call egx_trade_plan faster than any human can review — one bad instruction and it creates or modifies resources in Tradingview by the hundred, each call as confident as the last.
Attacks that exploit this kind of access
Generate a full trade plan for a specific EGX stock. It is categorised as a Write tool in the Tradingview MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Tradingview MCP server in PolicyLayer and add a rule for egx_trade_plan: 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_trade_plan is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the egx_trade_plan 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_trade_plan. 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_trade_plan 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 →