activate_tab
Switch to a specific Safari tab. Use list_tabs to find window/tab indices.
This record as markdown: /tools/io-github-heznpc-iconnect/activate-tab.md
What activate_tab does on Iconnect
AI agents invoke activate_tab to trigger actions in Iconnect. 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.
Why activate_tab is rated High
This tool triggers a browser action (switching tabs in Safari), which is an external operation affecting application state. It falls under Execute as it performs a UI/browser action rather than simply reading data or writing persistent data.
From the tool's definition Switch to a specific Safari tab
Attacks that exploit this kind of access
The rule that runs activate_tab safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Iconnect, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For activate_tab, this is the rule to start with:
activate_tab 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Iconnect, apply this rule, and every activate_tab call is checked against it from then on.
Questions about activate_tab
Switch to a specific Safari tab. Use list_tabs to find window/tab indices. It is categorised as a Execute tool in the Iconnect MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Iconnect MCP server in PolicyLayer and add a rule for activate_tab: 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 Iconnect. Nothing to install.
activate_tab 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 activate_tab 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 activate_tab. 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.
activate_tab is provided by the Iconnect MCP server (iconnect-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Iconnect, and thousands of servers like it.
Across the catalogue