Set the default device for subsequent operations
AI agents use adb_set_default_device to create or update resources in ADB MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your ADB MCP Server environment.
This tool creates or updates configuration state (designating a default device) that affects subsequent tool behavior. While reversible (another adb_set_default_device call can change it), it modifies persistent application state. Classified as Write rather than Read (it has side effects) or Execute (it doesn't run commands or trigger operations, just sets configuration).
From the tool's definition 'Set the default device for subsequent operations' - modifies configuration state that persists across operations.
Attacks that exploit this kind of access
Set the default device for subsequent operations. It is categorised as a Write tool in the ADB MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the ADB MCP Server MCP server in PolicyLayer and add a rule for adb_set_default_device: 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 ADB MCP Server. Nothing to install.
adb_set_default_device is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the adb_set_default_device 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.
Set action: deny in the PolicyLayer policy for adb_set_default_device. 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.
adb_set_default_device is provided by the ADB MCP Server MCP server (richard0913/adb-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →