adb_settings_put

Write an Android settings value to any namespace (system, secure, global)

SERVERDeepadb SOURCEdeepadb

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-fullread-deepadb/adb-settings-put.md

WHAT IT DOES

What adb_settings_put does on Deepadb

AI agents use adb_settings_put to create or update resources in Deepadb, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Deepadb environment.

RISK

Why adb_settings_put is rated Medium

This tool modifies Android system settings across multiple privileged namespaces (system, secure, global). While reversible (settings can be changed back), it can alter device behavior, security policies, and user experience in significant ways. The ability to write to 'secure' and 'global' namespaces grants access to sensitive configuration, justifying 'high' severity.

From the tool's definition Tool name 'adb_settings_put' and description 'Write an Android settings value to any namespace (system, secure, global)' explicitly indicate creation or modification of data. The verb 'Write' and 'put' confirm reversible data modification.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

adb_settings_put Rate-limited

adb_settings_put stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "adb_settings_put": {
      "limits": [
        {
          "counter": "adb_settings_put_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about adb_settings_put

What does the adb_settings_put tool do? +

Write an Android settings value to any namespace (system, secure, global). It is categorised as a Write tool in the Deepadb MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on adb_settings_put? +

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

adb_settings_put is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit adb_settings_put? +

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

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

adb_settings_put 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

Govern customer-ops agents →Argument validation →Scoped token →