AI agents call analyze_performance 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.
The tool appears to analyze/read performance metrics of an application, which is a read/query operation with no side effects. However, the description is minimal (Chinese: 'analyze application performance'), so confidence is moderate. Performance analysis typically involves reading CPU, memory, and other metrics without modifying state.
From the tool's definition Tool name 'analyze_performance' and description '分析应用性能' (analyze application performance)
Documented attack patterns abuse exactly the kind of access analyze_performance 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 analyze_performance:
{
"version": "1",
"default": "deny",
"tools": {
"analyze_performance": {}
}
}analyze_performance 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 analyze_performance: 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.
analyze_performance 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 analyze_performance 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 analyze_performance. 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.
analyze_performance 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.