Get the current connection status and configuration.
AI agents call get_connection_status to retrieve information from IBKR-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 connection status and configuration details from the IBKR API connection. It performs a query operation to obtain read-only state information. No financial transactions, data modifications, code execution, or destructive operations are possible.
From the tool's definition Tool name and description indicate 'Get the current connection status and configuration' - retrieval of status information with no side effects or data modification.
Documented attack patterns abuse exactly the kind of access get_connection_status gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and IBKR-MCP-Server, and nothing reaches the server without passing your rules. This is the rule we recommend for get_connection_status:
{
"version": "1",
"default": "deny",
"tools": {
"get_connection_status": {}
}
}get_connection_status 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.
Get the current connection status and configuration. It is categorised as a Read tool in the IBKR-MCP-Server MCP Server, which means it retrieves data without modifying state.
Register the IBKR-MCP-Server MCP server in PolicyLayer and add a rule for get_connection_status: 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-MCP-Server. Nothing to install.
get_connection_status 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_connection_status 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_connection_status. 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_connection_status is provided by the IBKR-MCP-Server MCP server (xiao81/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-MCP-Server, 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.
5 IBKR-MCP-Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.