This record as markdown: /tools/af7007-mcp-trader/orders-get.md
What orders_get does on MCP Trader Server
AI agents call orders_get to retrieve information from MCP Trader Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why orders_get is rated Low
This tool retrieves information about existing orders without creating, modifying, deleting, or executing any trades. It is a passive read operation that queries the current state of orders. While it operates within a financial trading context, the tool itself does not move money, create obligations, or execute transactions—it only provides visibility into existing order data.
From the tool's definition Tool name 'orders_get' and description 'Get active orders' indicate data retrieval with no modification or execution of trades.
Attacks that exploit this kind of access
The rule that runs orders_get safely
PolicyLayer is an MCP gateway: it sits between your AI agents and MCP Trader Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For orders_get, this is the rule to start with:
orders_get 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 MCP Trader Server, apply this rule, and every orders_get call is checked against it from then on.
Questions about orders_get
Get active orders. It is categorised as a Read tool in the MCP Trader Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Trader Server MCP server in PolicyLayer and add a rule for orders_get: 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 MCP Trader Server. Nothing to install.
orders_get 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 orders_get 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 orders_get. 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.
orders_get is provided by the MCP Trader Server MCP server (af7007/mcp-trader). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on MCP Trader Server, and thousands of servers like it.
This server
Across the catalogue