AI agents call app_current to retrieve information from uiautomator2 MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Based on the naming convention and context of sibling tools (app_info, app_list, app_list_running all appear to be read operations), 'app_current' most likely retrieves information about the currently running foreground application. This is a read operation with low blast radius. Confidence is reduced due to the empty description.
From the tool's definition Tool name 'app_current' suggests retrieving the currently active/foreground app; description is empty and uninformative.
Documented attack patterns abuse exactly the kind of access app_current gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and uiautomator2 MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for app_current:
{
"version": "1",
"default": "deny",
"tools": {
"app_current": {}
}
}app_current 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.
app_current. It is categorised as a Read tool in the uiautomator2 MCP Server MCP Server, which means it retrieves data without modifying state.
Register the uiautomator2 MCP Server MCP server in PolicyLayer and add a rule for app_current: 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 uiautomator2 MCP Server. Nothing to install.
app_current 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 app_current 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 app_current. 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.
app_current is provided by the uiautomator2 MCP Server MCP server (tanbro/uiautomator2-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from uiautomator2 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.
77 uiautomator2 MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.