Log in to the MetaTrader 5 trading account.
AI agents invoke login to trigger actions in MetaTrader 5 MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Logging into a MetaTrader 5 account initiates an authenticated session on a live trading platform, enabling subsequent financial operations. While it doesn't directly move money, it is an external operation that establishes access to a financial system with high-impact sibling tools (close_position, cancel_order, etc.).
From the tool's definition 'Log in to the MetaTrader 5 trading account' — triggers an external authentication/session operation against a live financial trading platform
Attacks that exploit this kind of access
Log in to the MetaTrader 5 trading account. It is categorised as a Execute tool in the MetaTrader 5 MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the MetaTrader 5 MCP Server MCP server in PolicyLayer and add a rule for login: 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 MetaTrader 5 MCP Server. Nothing to install.
login is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the login 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 login. 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.
login is provided by the MetaTrader 5 MCP Server MCP server (jorgearturoyap-debug/metatrader-5-for-chatgpt-desktop). 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 →