adb_current_activity

Get the currently focused activity and window stack

SERVERDeepadb SOURCEdeepadb

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/io-github-fullread-deepadb/adb-current-activity.md

WHAT IT DOES

What adb_current_activity does on Deepadb

AI agents call adb_current_activity to retrieve information from Deepadb 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_activity is rated Low

This tool retrieves information about the current state of the Android device (currently focused activity and window stack) without modifying, executing, or destroying anything. It is a straightforward query that returns data about the UI state. The blast radius of misuse is minimal—an agent could only learn what is currently displayed, which is low-risk information disclosure.

From the tool's definition Tool name and description indicate it 'Get the currently focused activity and window stack'—a query operation with no side effects. The verb 'get' and the passive nature of reading activity state confirms this is a read-only operation.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs adb_current_activity safely

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

adb_current_activity Allowed

adb_current_activity 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_activity": {}
  }
}

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

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

FAQ

Questions about adb_current_activity

What does the adb_current_activity tool do? +

Get the currently focused activity and window stack. It is categorised as a Read tool in the Deepadb MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on adb_current_activity? +

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

What risk level is adb_current_activity? +

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

Can I rate-limit adb_current_activity? +

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

How do I block adb_current_activity completely? +

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

What MCP server provides adb_current_activity? +

adb_current_activity is provided by the Deepadb MCP server (deepadb). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Deepadb, and thousands of servers like it.

This server

All 205 Deepadb tools →

Across the catalogue

The MCP Attack Database →

Guides

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