Manages browser tabs.
AI agents invoke tabs to trigger actions in Brave Browser MCP Server. 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.
Managing browser tabs implies executing browser-level operations (open new tab, close tab, switch focus, etc.). While some operations are reversible (switching tabs), others like closing tabs may not be (losing unsaved state). Given the server explicitly provides 'full control over Brave Browser', this tool likely includes tab creation and destruction.
From the tool's definition 'Manages browser tabs' — tab management involves opening, closing, switching, or otherwise controlling browser tabs, which are external browser operations with real side effects.
Attacks that exploit this kind of access
Manages browser tabs. It is categorised as a Execute tool in the Brave Browser MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Brave Browser MCP Server MCP server in PolicyLayer and add a rule for tabs: 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 Brave Browser MCP Server. Nothing to install.
tabs 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 tabs 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 tabs. 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.
tabs is provided by the Brave Browser MCP Server MCP server (slaveofgod1/brave-browser-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →