get_pending_orders
AI agents call get_pending_orders to retrieve information from IB Analytics MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves pending order information from Interactive Brokers without modifying, executing, or deleting anything. It queries existing state and returns data, making it a Read operation. The blast radius is minimal since viewing orders poses no immediate risk.
From the tool's definition Tool name 'get_pending_orders' indicates retrieval of existing order data. The empty description limits evidence, but the name follows a 'get_*' pattern consistent with data queries.
Attacks that exploit this kind of access
get_pending_orders. It is categorised as a Read tool in the IB Analytics MCP Server MCP Server, which means it retrieves data without modifying state.
Register the IB Analytics MCP Server MCP server in PolicyLayer and add a rule for get_pending_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 IB Analytics MCP Server. Nothing to install.
get_pending_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 get_pending_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 get_pending_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.
get_pending_orders is provided by the IB Analytics MCP Server MCP server (knishioka/ib-sec-mcp). 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 →