adb_list_splits

List all APK split paths installed for a package. Shows the base APK and any configuration splits (language, screen density, ABI).

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-list-splits.md

WHAT IT DOES

What adb_list_splits does on Deepadb

AI agents call adb_list_splits 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_list_splits is rated Low

This tool queries and returns data about installed APK splits on an Android device. It performs no mutations, deletions, execution of code, or financial operations. The information retrieved is already publicly visible to processes running on the device with standard permissions.

From the tool's definition Tool name contains 'list' and description states 'List all APK split paths installed for a package' — a pure query operation that retrieves and displays information without modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs adb_list_splits 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_list_splits, this is the rule to start with:

adb_list_splits Allowed

adb_list_splits 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_list_splits": {}
  }
}

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_list_splits call is checked against it from then on.

FAQ

Questions about adb_list_splits

What does the adb_list_splits tool do? +

List all APK split paths installed for a package. Shows the base APK and any configuration splits (language, screen density, ABI). 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_list_splits? +

Register the Deepadb MCP server in PolicyLayer and add a rule for adb_list_splits: 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_list_splits? +

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

Can I rate-limit adb_list_splits? +

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

Set action: deny in the PolicyLayer policy for adb_list_splits. 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_list_splits? +

adb_list_splits 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

aiva_list_affiliates on AIVA MCP Server →list_agents on 0rca Dojo MCP Server → The MCP Attack Database →

Guides

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