close_managed_tabs

关闭 BrowserPilot MCP 自身打开/使用过的 tab。默认只关参数里给定的 tabId(如果属于受管集合);传 allManaged=true 时关闭所有受管 tab。永远不关 Chrome 浏览器本身;如果关闭全部受管 tab 会导致最后一个窗口被清空,工具会改为仅从受管集合移除而不调用 chrome.tabs.remove。

Server BrowserPilot MCP sept-7-qi/browserpilot-mcp
Category Destructive
Risk class Critical
Parameters 00 required

What close_managed_tabs does on BrowserPilot MCP

AI agents call close_managed_tabs to permanently remove resources in BrowserPilot MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why close_managed_tabs needs a policy

Closing browser tabs is an irreversible destructive action — any unsaved state, form data, or session information in those tabs is permanently lost. The tool can close all managed tabs at once (allManaged=true), giving it a medium blast radius. It won't close the browser itself, which limits severity somewhat, but tab closure cannot be undone.

From the tool's definition 关闭 BrowserPilot MCP 自身打开/使用过的 tab...传 allManaged=true 时关闭所有受管 tab

Questions about close_managed_tabs

What does the close_managed_tabs tool do? +

关闭 BrowserPilot MCP 自身打开/使用过的 tab。默认只关参数里给定的 tabId(如果属于受管集合);传 allManaged=true 时关闭所有受管 tab。永远不关 Chrome 浏览器本身;如果关闭全部受管 tab 会导致最后一个窗口被清空,工具会改为仅从受管集合移除而不调用 chrome.tabs.remove。. It is categorised as a Destructive tool in the BrowserPilot MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on close_managed_tabs? +

Register the BrowserPilot MCP server in PolicyLayer and add a rule for close_managed_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 BrowserPilot MCP. Nothing to install.

What risk level is close_managed_tabs? +

close_managed_tabs is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit close_managed_tabs? +

Yes. Add a rate_limit block to the close_managed_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.

How do I block close_managed_tabs completely? +

Set action: deny in the PolicyLayer policy for close_managed_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.

What MCP server provides close_managed_tabs? +

close_managed_tabs is provided by the BrowserPilot MCP server (sept-7-qi/browserpilot-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.