adb_current_app

Gets the currently focused/active app on the Android device.

SERVERRenef SOURCEahmeth4n/renef-mcp

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/ahmeth4n-renef-mcp/adb-current-app.md

WHAT IT DOES

What adb_current_app does on Renef

AI agents call adb_current_app to retrieve information from Renef without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why adb_current_app is rated Low

This tool retrieves information about which app is currently in focus on an Android device. It performs no side effects, does not execute code, does not modify data, and does not delete or manipulate state.

From the tool's definition Tool name 'adb_current_app' and description 'Gets the currently focused/active app on the Android device' indicate a query operation that retrieves the state of the device without modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs adb_current_app safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Renef, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For adb_current_app, this is the rule to start with:

adb_current_app Allowed

adb_current_app is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "adb_current_app": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Renef, apply this rule, and every adb_current_app call is checked against it from then on.

FAQ

Questions about adb_current_app

What does the adb_current_app tool do? +

Gets the currently focused/active app on the Android device. It is categorised as a Read tool in the Renef MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on adb_current_app? +

Register the Renef MCP server in PolicyLayer and add a rule for adb_current_app: 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 Renef. Nothing to install.

What risk level is adb_current_app? +

adb_current_app is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit adb_current_app? +

Yes. Add a rate_limit block to the adb_current_app 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.

How do I block adb_current_app completely? +

Set action: deny in the PolicyLayer policy for adb_current_app. 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.

What MCP server provides adb_current_app? +

adb_current_app is provided by the Renef MCP server (ahmeth4n/renef-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Renef, and thousands of servers like it.

This server

All 75 Renef tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →