This record as markdown: /tools/io-github-heznpc-iconnect/get-current-tab.md
What get_current_tab does on Iconnect
AI agents call get_current_tab to retrieve information from Iconnect without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why get_current_tab is rated Low
This tool retrieves information about the currently active Safari browser tab (its title and URL). It performs a query operation with no side effects—it neither modifies data, executes code, deletes anything, nor commits financial transactions. The risk is low because exposure of tab metadata poses minimal security harm compared to tools that can modify browser state or execute arbitrary code.
From the tool's definition Tool name 'get_current_tab' and description 'Get the title and URL of the active Safari tab' indicate data retrieval with no modification or execution of external operations.
Attacks that exploit this kind of access
The rule that runs get_current_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 get_current_tab, this is the rule to start with:
get_current_tab is read-only, so it stays allowed. 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 get_current_tab call is checked against it from then on.
Questions about get_current_tab
Get the title and URL of the active Safari tab. It is categorised as a Read tool in the Iconnect MCP Server, which means it retrieves data without modifying state.
Register the Iconnect MCP server in PolicyLayer and add a rule for get_current_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.
get_current_tab 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_current_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 get_current_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.
get_current_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.
This server
Across the catalogue