Get recent trade executions/fills.
AI agents call get_executions to retrieve information from IB Portfolio Tracker MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves past trade execution records from an Interactive Brokers account. It is a read operation that accesses financial transaction history. While the data retrieved is sensitive (execution details that could reveal trading strategy), the tool itself performs no modifications, deletions, or financial transfers.
From the tool's definition Tool name is 'get_executions' with description 'Get recent trade executions/fills.' This retrieves historical transaction data without modifying or deleting anything.
Attacks that exploit this kind of access
Get recent trade executions/fills. It is categorised as a Read tool in the IB Portfolio Tracker MCP Server MCP Server, which means it retrieves data without modifying state.
Register the IB Portfolio Tracker MCP Server MCP server in PolicyLayer and add a rule for 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 IB Portfolio Tracker MCP Server. Nothing to install.
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 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 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.
get_executions is provided by the IB Portfolio Tracker MCP Server MCP server (vinbg/ib-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →