Return open orders with contract details and status.
AI agents call ibkr_get_open_orders to retrieve information from Ibkr without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and returns information about open orders. It has no side effects—it does not cancel, modify, execute, or delete orders. It is purely informational, similar to other Read tools on the server like ibkr_get_account_summary and ibkr_get_executions. The blast radius of misuse is minimal since viewing order data does not directly affect trading positions or finances.
From the tool's definition Tool name 'ibkr_get_open_orders' and description 'Return open orders with contract details and status' indicate a retrieval operation that queries existing order data without modification or execution.
Documented attack patterns abuse exactly the kind of access ibkr_get_open_orders gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Ibkr, and nothing reaches the server without passing your rules. This is the rule we recommend for ibkr_get_open_orders:
{
"version": "1",
"default": "deny",
"tools": {
"ibkr_get_open_orders": {}
}
}ibkr_get_open_orders is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Return open orders with contract details and status. It is categorised as a Read tool in the Ibkr MCP Server, which means it retrieves data without modifying state.
Register the Ibkr MCP server in PolicyLayer and add a rule for ibkr_get_open_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 Ibkr. Nothing to install.
ibkr_get_open_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 ibkr_get_open_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 ibkr_get_open_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.
ibkr_get_open_orders is provided by the Ibkr MCP server (patrickpxp/ibkr-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Ibkr, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
33 Ibkr tools catalogued and risk-classified — across an index of 43,000+ MCP servers.