获取当前前台活动的应用和Activity
AI agents call get_current_activity 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.
This tool queries the current active application and Activity on an Android device. It retrieves information about what is presently displayed but does not modify device state, execute commands, delete data, or move resources. This is a straightforward read operation with minimal security risk if misused—an agent would only obtain information about the currently active app, which is low-impact.
From the tool's definition Tool name 'get_current_activity' and description 'retrieves the current foreground application and Activity' indicate a query operation that reads state information without modification or side effects.
Documented attack patterns abuse exactly the kind of access get_current_activity 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 get_current_activity:
{
"version": "1",
"default": "deny",
"tools": {
"get_current_activity": {}
}
}get_current_activity 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.
获取当前前台活动的应用和Activity. 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 get_current_activity: 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.
get_current_activity 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 get_current_activity 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 get_current_activity. 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.
get_current_activity 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.