AI agents invoke new_tab 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.
Opening URLs in a controlled browser constitutes Execute risk: it initiates network operations and loads arbitrary web content that may execute scripts, trigger side effects, or interact with external services. An AI agent could be tricked into opening malicious URLs, performing phishing, or executing unintended actions on third-party sites.
From the tool's definition Tool controls a browser to 'open a new tab and open a URL' (翻译: 'open new tab and open a URL'). This is browser automation that triggers external operations—network requests, page loading, JavaScript execution—whose effects depend on the URL argument.
Documented attack patterns abuse exactly the kind of access new_tab 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 new_tab:
{
"version": "1",
"default": "deny",
"tools": {
"new_tab": {
"limits": [
{
"counter": "new_tab_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}new_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.
Free to start. No card required.
用DrissionPage 控制的浏览器,打开新标签页并 打开一个网址. 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 new_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 DrissionPageMCP. Nothing to install.
new_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 new_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 new_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.
new_tab 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.