Low Risk

get_current_tab_screenshot_as_file

获取当前标签页的屏幕截图并保存为文件 Args: path (str): 截图保存路径,默认为当前目录 Returns: str: 截图的文件路径

How to control get_current_tab_screenshot_as_file ↓

AI agents call get_current_tab_screenshot_as_file 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.

Low Risk

This tool captures a screenshot of the current browser tab and saves it to disk. It reads/captures visual state without modifying any data or triggering external operations. Writing a file to disk is a minor side effect but the primary action is reading/capturing the screen state. Severity is low as it only captures what is currently visible in the browser.

From the tool's definition 获取当前标签页的屏幕截图并保存为文件 (Gets a screenshot of the current tab and saves it as a file)

Documented attack patterns abuse exactly the kind of access get_current_tab_screenshot_as_file 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_as_file:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_current_tab_screenshot_as_file": {}
  }
}

get_current_tab_screenshot_as_file is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register DrissionPageMCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Go deeper

What does the get_current_tab_screenshot_as_file tool do? +

获取当前标签页的屏幕截图并保存为文件 Args: path (str): 截图保存路径,默认为当前目录 Returns: str: 截图的文件路径. It is categorised as a Read tool in the DrissionPageMCP MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_current_tab_screenshot_as_file? +

Register the DrissionPage MCP server in PolicyLayer and add a rule for get_current_tab_screenshot_as_file: 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.

What risk level is get_current_tab_screenshot_as_file? +

get_current_tab_screenshot_as_file is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_current_tab_screenshot_as_file? +

Yes. Add a rate_limit block to the get_current_tab_screenshot_as_file 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.

How do I block get_current_tab_screenshot_as_file completely? +

Set action: deny in the PolicyLayer policy for get_current_tab_screenshot_as_file. 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.

What MCP server provides get_current_tab_screenshot_as_file? +

get_current_tab_screenshot_as_file 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.

Enforce policy on every DrissionPageMCP tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.