This record as markdown: /tools/io-github-homenshum-nodebench/nb-switch-research-tab.md
What nb_switch_research_tab does on Nodebench
AI agents invoke nb_switch_research_tab to trigger actions in Nodebench. 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 nb_switch_research_tab is rated High
Switching a tab is a browser/UI action that changes the active state of the application. It falls under Execute as it triggers an external operation (UI navigation). It is not purely reading data, and it changes application state, though the blast radius is relatively limited. Confidence is moderate because the description is sparse and does not detail side effects.
From the tool's definition 'Switch the research hub tab' — triggers a UI/browser action that changes application state
Attacks that exploit this kind of access
The rule that runs nb_switch_research_tab safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Nodebench, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For nb_switch_research_tab, this is the rule to start with:
nb_switch_research_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 Nodebench, apply this rule, and every nb_switch_research_tab call is checked against it from then on.
Questions about nb_switch_research_tab
Switch the research hub tab. It is categorised as a Execute tool in the Nodebench MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Nodebench MCP server in PolicyLayer and add a rule for nb_switch_research_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 Nodebench. Nothing to install.
nb_switch_research_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 nb_switch_research_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 nb_switch_research_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.
nb_switch_research_tab is provided by the Nodebench MCP server (nodebench-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Nodebench, and thousands of servers like it.
Across the catalogue