AI agents call get_tab_list to retrieve information from DrissionPageMCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns data about open browser tabs without side effects, state changes, or triggering any actions. It is a straightforward read operation that fits the 'Read' category (retrieve/query data with no side effects). The low severity reflects minimal security risk even if misused by an untrusted agent, as it only exposes already-visible browser state.
From the tool's definition Tool name is 'get_tab_list' and description states it 'retrieves...all tab information, including url, title, id' from the current browser—purely informational retrieval with no modification or execution.
Documented attack patterns abuse exactly the kind of access get_tab_list 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 get_tab_list:
{
"version": "1",
"default": "deny",
"tools": {
"get_tab_list": {}
}
}get_tab_list is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
获取当前浏览器的所有标签页的信息,包括url, title, id. It is categorised as a Read tool in the DrissionPageMCP MCP Server, which means it retrieves data without modifying state.
Register the DrissionPage MCP server in PolicyLayer and add a rule for get_tab_list: 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.
get_tab_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_tab_list 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 get_tab_list. 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.
get_tab_list 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.