New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

adb_get_current_activity

Get the foreground activity.

SERVERLocalAnt SOURCEyuga-hashimoto/localant
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/yuga-hashimoto-localant/adb-get-current-activity.md

What adb_get_current_activity does on LocalAnt

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

Why adb_get_current_activity is rated Low

This tool retrieves information about which Android activity is currently displayed on screen. It performs a read-only query with no side effects—it does not modify the device state, execute code, delete data, or trigger financial transactions. The limited scope (querying current foreground state) and informational nature place it firmly in the Read category.

From the tool's definition Tool name 'adb_get_current_activity' and description 'Get the foreground activity' indicate a query operation that retrieves the current state of the Android foreground without modification or execution of commands.

Questions about adb_get_current_activity

What does the adb_get_current_activity tool do? +

Get the foreground activity. It is categorised as a Read tool in the LocalAnt MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on adb_get_current_activity? +

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

What risk level is adb_get_current_activity? +

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

Can I rate-limit adb_get_current_activity? +

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

How do I block adb_get_current_activity completely? +

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

What MCP server provides adb_get_current_activity? +

adb_get_current_activity is provided by the LocalAnt MCP server (yuga-hashimoto/localant). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

More on LocalAnt, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of LocalAnt's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.