Return executions/fills matching the provided filters.
AI agents call ibkr_get_executions 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 historical execution and fill data from an IBKR account, which is a read-only operation that queries existing information without side effects. However, the severity is elevated to 'medium' rather than 'low' because executions and fills contain sensitive financial transaction history that could enable account reconnaissance or inform unauthorized trading decisions if misused by an agent.
From the tool's definition Tool name 'ibkr_get_executions' and description 'Return executions/fills matching the provided filters' indicate a query/retrieval operation with no modification of data.
Documented attack patterns abuse exactly the kind of access ibkr_get_executions 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_executions:
{
"version": "1",
"default": "deny",
"tools": {
"ibkr_get_executions": {}
}
}ibkr_get_executions 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 executions/fills matching the provided filters. 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_executions: 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_executions 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_executions 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_executions. 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_executions 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.