adb_carrier_config

Dump carrier configuration values. Useful for verifying carrier settings, detecting configuration anomalies, and inspecting APN configurations.

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-carrier-config.md

WHAT IT DOES

What adb_carrier_config does on Deepadb

AI agents call adb_carrier_config 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_carrier_config is rated Low

This tool retrieves and inspects carrier configuration data from an Android device via ADB. It performs no modifications, deletions, or side effects—purely a read operation to examine existing configuration state. The low severity reflects that querying carrier settings on a device poses minimal risk even if misused by an AI agent.

From the tool's definition Tool name is 'adb_carrier_config' and description states it 'Dump carrier configuration values' for 'verifying carrier settings, detecting configuration anomalies, and inspecting APN configurations.' The verb 'dump' and use cases (verifying, detecting,…

Attacks that exploit this kind of access

RECOMMENDED RULE

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

adb_carrier_config Allowed

adb_carrier_config 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_carrier_config": {}
  }
}

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

FAQ

Questions about adb_carrier_config

What does the adb_carrier_config tool do? +

Dump carrier configuration values. Useful for verifying carrier settings, detecting configuration anomalies, and inspecting APN configurations. 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_carrier_config? +

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

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

Can I rate-limit adb_carrier_config? +

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

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

adb_carrier_config 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 →