Close all opened profiles on the current device
AI agents invoke close-all-profiles to trigger actions in TgeBrowser 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.
Closing all opened browser profiles is an operational action that terminates running browser sessions across the entire device. It is not a simple read and not necessarily irreversible (profiles can be reopened), but it triggers a broad external operation affecting all active sessions simultaneously.
From the tool's definition Close all opened profiles on the current device
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Close all opened profiles on the current device. It is categorised as a Execute tool in the TgeBrowser MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the TgeBrowser MCP Server MCP server in PolicyLayer and add a rule for close-all-profiles: 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 TgeBrowser MCP Server. Nothing to install.
close-all-profiles 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 close-all-profiles 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 close-all-profiles. 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.
close-all-profiles is provided by the TgeBrowser MCP Server MCP server (tuguang2025/tgebrowser-mcp-server). 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 →