trade_get_pending
Get pending orders. Compact output omits echoed request metadata by default.
This record as markdown: /tools/emerzon-mt-data-mcp/trade-get-pending.md
What trade_get_pending does on MetaTrader5 MCP Server
AI agents call trade_get_pending to retrieve information from MetaTrader5 MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why trade_get_pending is rated Low
This tool retrieves pending order information from MetaTrader5 without creating, modifying, or deleting any data. It is purely informational—a read operation on existing trading state. While the context involves financial instruments and trading, the tool itself performs no financial transactions, does not execute trades, and cannot commit financial obligations.
From the tool's definition Tool name 'trade_get_pending' and description 'Get pending orders' indicate a retrieval operation with no modification capability. The phrase 'Get' and 'Compact output omits echoed request metadata' confirm read-only query semantics.
Attacks that exploit this kind of access
The rule that runs trade_get_pending safely
PolicyLayer is an MCP gateway: it sits between your AI agents and MetaTrader5 MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For trade_get_pending, this is the rule to start with:
trade_get_pending is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect MetaTrader5 MCP Server, apply this rule, and every trade_get_pending call is checked against it from then on.
Questions about trade_get_pending
Get pending orders. Compact output omits echoed request metadata by default. It is categorised as a Read tool in the MetaTrader5 MCP Server MCP Server, which means it retrieves data without modifying state.
Register the MetaTrader5 MCP Server MCP server in PolicyLayer and add a rule for trade_get_pending: 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 MetaTrader5 MCP Server. Nothing to install.
trade_get_pending 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 trade_get_pending 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 trade_get_pending. 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.
trade_get_pending is provided by the MetaTrader5 MCP Server MCP server (emerzon/mt-data-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on MetaTrader5 MCP Server, and thousands of servers like it.
This server
Across the catalogue