Inspect current focused app/window via dumpsys window.
AI agents call get-current-activity to retrieve information from Android Mcp Toolkit without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves application and window state data through Android's dumpsys diagnostic service. While it does not modify data (hence not Write), it can expose sensitive information about which apps are currently running and in focus, which could be misused by an agent to spy on user activity or gather reconnaissance on the system.
From the tool's definition Tool uses 'dumpsys window' to inspect the current focused app/window. This is a read-only query operation that retrieves system state information without modifying or executing anything.
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 Android Mcp Toolkit, 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.
Inspect current focused app/window via dumpsys window. It is categorised as a Read tool in the Android Mcp Toolkit MCP Server, which means it retrieves data without modifying state.
Register the Android Mcp Toolkit 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 Android Mcp Toolkit. 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 Android Mcp Toolkit MCP server (nam0101/android-mcp-toolkit). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Android Mcp Toolkit, 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.
7 Android Mcp Toolkit tools catalogued and risk-classified — across an index of 43,000+ MCP servers.