List pending limit/stop orders with ticket, symbol, type, volume, and trigger price
AI agents call get_orders to retrieve information from XBTFX MCP Trading Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The get_orders tool retrieves and displays information about pending orders. This is a read-only operation with no side effects on account state, positions, or financial obligations. It falls clearly into the Read category. Severity is low because querying order data poses minimal risk even if an AI agent misuses it—it cannot directly harm the account, execute unauthorized trades, or move funds.
From the tool's definition Tool description states 'List pending limit/stop orders' - a retrieval operation that queries existing order data without modification, creation, or execution of trades.
Attacks that exploit this kind of access
List pending limit/stop orders with ticket, symbol, type, volume, and trigger price. It is categorised as a Read tool in the XBTFX MCP Trading Server MCP Server, which means it retrieves data without modifying state.
Register the XBTFX MCP Trading Server MCP server in PolicyLayer and add a rule for get_orders: 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 XBTFX MCP Trading Server. Nothing to install.
get_orders 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 get_orders 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 get_orders. 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.
get_orders is provided by the XBTFX MCP Trading Server MCP server (xbtfx/xbtfx-mcp-server). 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 →