ibkr_get_trade_confirmations
AI agents call ibkr_get_trade_confirmations 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 trade confirmation records from an Interactive Brokers account — a read-only operation with no side effects. However, severity is elevated to 'high' because trade confirmations contain sensitive financial data (transaction details, counterparties, amounts) that could expose account activity and positions if misused by an untrusted AI agent.
From the tool's definition Tool name 'ibkr_get_trade_confirmations' indicates retrieval of trade confirmation data. Server description states it exposes 'account data, portfolio positions, orders, executions, contracts, and market data snapshots via MCP' — all read operations.
Documented attack patterns abuse exactly the kind of access ibkr_get_trade_confirmations 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_trade_confirmations:
{
"version": "1",
"default": "deny",
"tools": {
"ibkr_get_trade_confirmations": {}
}
} ibkr_get_trade_confirmations 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.
ibkr_get_trade_confirmations. 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_trade_confirmations: 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_trade_confirmations 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_trade_confirmations 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_trade_confirmations. 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_trade_confirmations 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.