AI agents call get_scanner_parameters to retrieve information from Ib Async without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries configuration or reference data from the Interactive Brokers API. It does not create, modify, delete, or execute actions—it only retrieves parameter definitions that users need to construct scanner queries. The blast radius of misuse is minimal; an agent obtaining scanner parameters cannot directly harm accounts, delete data, or commit financial transactions.
From the tool's definition The tool 'get_scanner_parameters' retrieves available scanner parameters with no modification of data. The verb 'get' and the passive framing ('available parameters') indicate a read-only operation that returns metadata about scanning options without side…
Attacks that exploit this kind of access
Get available scanner parameters. It is categorised as a Read tool in the Ib Async MCP Server, which means it retrieves data without modifying state.
Register the Ib Async MCP server in PolicyLayer and add a rule for get_scanner_parameters: 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 Async. Nothing to install.
get_scanner_parameters 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_scanner_parameters 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_scanner_parameters. 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_scanner_parameters is provided by the Ib Async MCP server (nadavgb-atom/ib-async-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 →