Run a market scanner subscription and return ranked results.
AI agents invoke ibkr_run_scanner to trigger actions in Ibkr. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool triggers an external operation (market scanner subscription) whose effects depend on scanner parameters and configuration. While it retrieves data (ranked results), the primary action is executing a subscription-based scanning process, which is characteristic of Execute category.
From the tool's definition Tool name 'ibkr_run_scanner' and description 'Run a market scanner subscription and return ranked results' indicate active execution of a market scanning operation.
Documented attack patterns abuse exactly the kind of access ibkr_run_scanner 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_run_scanner:
{
"version": "1",
"default": "deny",
"tools": {
"ibkr_run_scanner": {
"limits": [
{
"counter": "ibkr_run_scanner_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}ibkr_run_scanner stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Run a market scanner subscription and return ranked results. It is categorised as a Execute tool in the Ibkr MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Ibkr MCP server in PolicyLayer and add a rule for ibkr_run_scanner: 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_run_scanner is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the ibkr_run_scanner 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_run_scanner. 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_run_scanner 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.