android_current_app

Get the currently focused app and activity on the Android device.

SERVERDialogbrain SOURCEhttps://api.dialogbrain.com/mcp

Low RISK CLASS

Category Read

Parameters 10 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-saloprj-dialogbrain/android-current-app.md

WHAT IT DOES

What android_current_app does on Dialogbrain

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

Parameter	Type	Required	Description
`channel_account_id`	integer	—	Android device channel_account ID. Omit when the workspace has a single Android device; REQUIRED when it has more than one (e.g. WhatsApp + LINE), else the call

Parameters from the server's own tool schema.

RISK

Why android_current_app is rated Low

Even though android_current_app only reads data, uncontrolled read access leaks sensitive information and racks up API costs: an agent caught in a retry loop can make thousands of calls a minute without anyone noticing.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs android_current_app safely

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

android_current_app Allowed

android_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": {
    "android_current_app": {}
  }
}

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

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

FAQ

Questions about android_current_app

What does the android_current_app tool do? +

Get the currently focused app and activity on the Android device. It is categorised as a Read tool in the Dialogbrain MCP Server, which means it retrieves data without modifying state.

What parameters does android_current_app accept? +

android_current_app accepts 1 parameter: channel_account_id. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on android_current_app? +

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

What risk level is android_current_app? +

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

Can I rate-limit android_current_app? +

Yes. Add a rate_limit block to the android_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 android_current_app completely? +

Set action: deny in the PolicyLayer policy for android_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 android_current_app? +

android_current_app is provided by the Dialogbrain MCP server (https://api.dialogbrain.com/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Dialogbrain, and thousands of servers like it.

This server

All 225 Dialogbrain tools →

Across the catalogue

The MCP Attack Database →

Guides

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