adb_screenrecord
Record a short MP4 screen capture through adb shell screenrecord and pull it locally.
This record as markdown: /tools/io-github-vmoranv-jshookmcp/adb-screenrecord.md
What adb_screenrecord does on Jshookmcp
AI agents call adb_screenrecord to retrieve information from Jshookmcp without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why adb_screenrecord is rated Low
Records device screen without modification, but exposes sensitive visual data including credentials, private messages, and user activity.
From the tool's definition Record screen capture through adb shell screenrecord and pull locally
Attacks that exploit this kind of access
The rule that runs adb_screenrecord safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Jshookmcp, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For adb_screenrecord, this is the rule to start with:
adb_screenrecord is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Jshookmcp, apply this rule, and every adb_screenrecord call is checked against it from then on.
Questions about adb_screenrecord
Record a short MP4 screen capture through adb shell screenrecord and pull it locally. It is categorised as a Read tool in the Jshookmcp MCP Server, which means it retrieves data without modifying state.
Register the Jshook MCP server in PolicyLayer and add a rule for adb_screenrecord: 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 Jshookmcp. Nothing to install.
adb_screenrecord 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 adb_screenrecord 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 adb_screenrecord. 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.
adb_screenrecord is provided by the Jshook MCP server (@jshookmcp/jshook). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Jshook, and thousands of servers like it.
This server
Across the catalogue