用DrissionPage 打开或者接管已打开的浏览器，参数通过字典传递。如果url不为空则打开指定网址。 参数: params (dict): 包含以下可选键的字典： - url (str, 可选): 要打开的网址。如果未提供则不自动打开页面。 - debug_port (int, 可选): 调试端口，默认9222。 - browser_path (str, 可选): 浏览器可执行文件路径。 - headless (bool, 可选): 是否以无头模式启动浏览器，默认False。 - use_system_user_path (bool, 可选): 是否使用系统默认用户配置，默认Fal...
AI agents invoke connect_or_open_browser to trigger actions in DrissionPageMCP. 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.
This tool launches or hijacks a Chrome browser instance and optionally navigates to a URL. It triggers an external operation (browser process) whose effects depend on arguments — matching the Execute category. Misuse could expose the user's browser session, cookies, or allow navigation to malicious URLs, making severity high.
From the tool's definition 打开或者接管已打开的浏览器 (open or take over an already-opened browser); triggers browser launch/navigation with parameters like url, browser_path, headless mode
Documented attack patterns abuse exactly the kind of access connect_or_open_browser gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and DrissionPageMCP, and nothing reaches the server without passing your rules. This is the rule we recommend for connect_or_open_browser:
{
"version": "1",
"default": "deny",
"tools": {
"connect_or_open_browser": {
"limits": [
{
"counter": "connect_or_open_browser_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}connect_or_open_browser 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.
Free to start. No card required.
用DrissionPage 打开或者接管已打开的浏览器，参数通过字典传递。如果url不为空则打开指定网址。 参数: params (dict): 包含以下可选键的字典： - url (str, 可选): 要打开的网址。如果未提供则不自动打开页面。 - debug_port (int, 可选): 调试端口，默认9222。 - browser_path (str, 可选): 浏览器可执行文件路径。 - headless (bool, 可选): 是否以无头模式启动浏览器，默认False。 - use_system_user_path (bool, 可选): 是否使用系统默认用户配置，默认False。 返回: srt: 浏览器各种信息. It is categorised as a Execute tool in the DrissionPageMCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the DrissionPage MCP server in PolicyLayer and add a rule for connect_or_open_browser: 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 DrissionPageMCP. Nothing to install.
connect_or_open_browser 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 connect_or_open_browser 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 connect_or_open_browser. 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.
connect_or_open_browser is provided by the DrissionPage MCP server (wxhzhwxhzh/drissionpagemcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 37 DrissionPageMCP tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
37 DrissionPageMCP tools catalogued and risk-classified — across an index of 42,500+ MCP servers.