Place an IBKR order. Defaults to dry_run=true and transmit=false for safety.
AI agents use ibkr_place_order to commit financial operations through Ibkr — usually the final step of a payment, billing, or trading workflow. A call moves real money.
This tool interacts with a brokerage platform to place orders for financial instruments. Even with dry_run and transmit=false defaults, the tool's core function is to execute trades/orders which constitutes a financial action. If misused by an AI agent with transmit=true and dry_run=false, it could commit real financial obligations, making this a critical Financial-category tool.
From the tool's definition Place an IBKR order" — directly places financial orders through Interactive Brokers; despite safety defaults (dry_run=true, transmit=false), the tool is capable of committing real financial obligations when those defaults are overridden
Documented attack patterns abuse exactly the kind of access ibkr_place_order 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_place_order:
{
"version": "1",
"default": "deny",
"tools": {
"ibkr_place_order": {
"deny_if": [
{
"conditions": [],
"on_deny": "Requires human approval."
}
]
}
}
} Any call to ibkr_place_order is blocked until a human approves it. The rest of the server keeps working.
Free to start. No card required.
Place an IBKR order. Defaults to dry_run=true and transmit=false for safety. It is categorised as a Financial tool in the Ibkr MCP Server, which means it involves financial transactions. Block by default and require explicit approval.
Register the Ibkr MCP server in PolicyLayer and add a rule for ibkr_place_order: 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_place_order is a Financial tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the ibkr_place_order 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_place_order. 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_place_order 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.