AI agents call collect_device_logs 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.
Log collection is fundamentally a retrieval operation with no side effects. It queries and extracts diagnostic information from the device without creating, modifying, or deleting data. While the description is minimal (Chinese: '收集设备日志' = 'collect device logs'), the name clearly indicates read-only log retrieval.
From the tool's definition Tool name 'collect_device_logs' and description indicate retrieval of log data from Android devices. The term 'collect' combined with 'logs' denotes a read-only operation that gathers existing diagnostic information without modifying system state.
Documented attack patterns abuse exactly the kind of access collect_device_logs 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 collect_device_logs:
{
"version": "1",
"default": "deny",
"tools": {
"collect_device_logs": {}
}
}collect_device_logs 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 collect_device_logs: 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.
collect_device_logs 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 collect_device_logs 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 collect_device_logs. 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.
collect_device_logs 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.