This record as markdown: /tools/io-github-fullread-deepadb/adb-dumpsys.md
What adb_dumpsys does on Deepadb
AI agents invoke adb_dumpsys to trigger actions in Deepadb. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
Why adb_dumpsys is rated High
dumpsys is a system command that runs external operations on the Android device to retrieve system service state and debug information. This is an Execute category tool because it triggers external operations (dumpsys commands) whose effects and information disclosure depend on which service argument is specified.
From the tool's definition Tool name 'adb_dumpsys' and description 'Run dumpsys for a specific service' indicate execution of the Android dumpsys command, which executes system-level diagnostic queries on the target Android device.
Attacks that exploit this kind of access
The rule that runs adb_dumpsys safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Deepadb, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For adb_dumpsys, this is the rule to start with:
adb_dumpsys stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Deepadb, apply this rule, and every adb_dumpsys call is checked against it from then on.
Questions about adb_dumpsys
Run dumpsys for a specific service. Use. It is categorised as a Execute tool in the Deepadb MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Deepadb MCP server in PolicyLayer and add a rule for adb_dumpsys: 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 Deepadb. Nothing to install.
adb_dumpsys is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the adb_dumpsys 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_dumpsys. 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_dumpsys is provided by the Deepadb MCP server (deepadb). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Deepadb, and thousands of servers like it.
Across the catalogue