device_set_target

Switch active platform (android/ios/desktop/aurora/browser)

SERVERClaude Mobile SOURCEalexgladkov/claude-in-mobile

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/alexgladkov-claude-in-mobile/device-set-target.md

WHAT IT DOES

What device_set_target does on Claude Mobile

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

RISK

Why device_set_target is rated Medium

This tool changes the active/target platform configuration. It modifies state (which platform is being targeted) in a reversible way — you can switch back. No data is deleted, no code is executed, and no financial operations occur.

From the tool's definition Switch active platform (android/ios/desktop/aurora/browser)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs device_set_target safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Claude Mobile, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For device_set_target, this is the rule to start with:

device_set_target Rate-limited

device_set_target 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": {
    "device_set_target": {
      "limits": [
        {
          "counter": "device_set_target_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 Claude Mobile, apply this rule, and every device_set_target call is checked against it from then on.

FAQ

Questions about device_set_target

What does the device_set_target tool do? +

Switch active platform (android/ios/desktop/aurora/browser). It is categorised as a Write tool in the Claude Mobile MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on device_set_target? +

Register the Claude Mobile MCP server in PolicyLayer and add a rule for device_set_target: 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 Claude Mobile. Nothing to install.

What risk level is device_set_target? +

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

Can I rate-limit device_set_target? +

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

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

device_set_target is provided by the Claude Mobile MCP server (alexgladkov/claude-in-mobile). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Claude Mobile, and thousands of servers like it.

This server

All 198 Claude Mobile tools →

Across the catalogue

emit_assumption_set on 0sec →set-prioity on Kanban MCP Server →team_manager_set_sources on Team Manager MCP → The MCP Attack Database →

Guides

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