AI agents call take_screen_recording to retrieve information from Adb without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool captures/records the device screen, which is a read/capture operation. However, it has medium severity because screen recordings can capture sensitive information (passwords, PII, private content) visible on the screen, making misuse potentially privacy-invasive even though it doesn't modify system state.
From the tool's definition 录制设备屏幕视频 (Record device screen video)
Documented attack patterns abuse exactly the kind of access take_screen_recording gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Adb, and nothing reaches the server without passing your rules. This is the rule we recommend for take_screen_recording:
{
"version": "1",
"default": "deny",
"tools": {
"take_screen_recording": {}
}
}take_screen_recording 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.
录制设备屏幕视频. It is categorised as a Read tool in the Adb MCP Server, which means it retrieves data without modifying state.
Register the Adb MCP server in PolicyLayer and add a rule for take_screen_recording: 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 Adb. Nothing to install.
take_screen_recording 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 take_screen_recording 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 take_screen_recording. 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.
take_screen_recording is provided by the Adb MCP server (wolfcoming/adb_mcp_server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Adb, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
48 Adb tools catalogued and risk-classified — across an index of 43,000+ MCP servers.