AI agents call get_current_tab_screenshot 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 retrieves a visual snapshot of the current browser tab state. It performs only a read operation—capturing and returning screenshot data without modifying, deleting, executing code, or creating financial obligations. The action is non-destructive and has no lasting side effects on the browser state or underlying systems.
From the tool's definition Tool name 'get_current_tab_screenshot' and description '获取当前标签页的网页截图' (get current tab webpage screenshot) indicates retrieval of visual data from the browser. Returns bytes of screenshot binary data with no modification or side effects.
Documented attack patterns abuse exactly the kind of access get_current_tab_screenshot 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_current_tab_screenshot:
{
"version": "1",
"default": "deny",
"tools": {
"get_current_tab_screenshot": {}
}
}get_current_tab_screenshot 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.
获取当前标签页的网页截图 Returns: bytes: 截图的二进制数据. 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_current_tab_screenshot: 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_current_tab_screenshot 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_current_tab_screenshot 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_current_tab_screenshot. 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_current_tab_screenshot 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.