calculate_lot_size
AI agents invoke calculate_lot_size 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.
The tool exists on a trading/financial server alongside tools like calculate_margin, calculate_profit, and close_position. 'Calculate_lot_size' most likely computes a position size (lot size) for trading purposes. If it only computes/returns a value without placing orders, it would be Read; however, on MT5 servers such functions can trigger order sizing logic or feed directly into trade execution.
From the tool's definition Tool name 'calculate_lot_size' on a MetaTrader 5 trading server; description is empty and uninformative.
Attacks that exploit this kind of access
calculate_lot_size. 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 calculate_lot_size: 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.
calculate_lot_size 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 calculate_lot_size 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 calculate_lot_size. 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.
calculate_lot_size 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 →