AI agents call cpu-info to retrieve information from ADB MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool reads CPU usage metrics from the Android device, which is a non-destructive information retrieval operation. There is no capability to modify system state, execute commands, or cause side effects. This falls squarely into the Read category with low severity since CPU information is non-sensitive metadata that an agent could safely query.
From the tool's definition Tool name is 'cpu-info' and description translates to 'View device CPU usage situation'. This is a query operation that retrieves system information without modifying or executing actions on the device.
Documented attack patterns abuse exactly the kind of access cpu-info gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and ADB MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for cpu-info:
{
"version": "1",
"default": "deny",
"tools": {
"cpu-info": {}
}
}cpu-info 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.
查看设备CPU使用情况. It is categorised as a Read tool in the ADB MCP Server MCP Server, which means it retrieves data without modifying state.
Register the ADB MCP Server MCP server in PolicyLayer and add a rule for cpu-info: 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 MCP Server. Nothing to install.
cpu-info 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 cpu-info 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 cpu-info. 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.
cpu-info is provided by the ADB MCP Server MCP server (jiantao88/android-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from ADB MCP Server, 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.
30 ADB MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.