device_get_target

Get current active platform and status

SERVERClaude Mobile SOURCEalexgladkov/claude-in-mobile

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

WHAT IT DOES

What device_get_target does on Claude Mobile

AI agents call device_get_target to retrieve information from Claude Mobile without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why device_get_target is rated Low

This tool queries and returns the current state of a mobile device (active platform and status). It performs a simple information retrieval operation analogous to a status check, with no capability to modify device state, execute commands, or cause side effects. This is a classic Read category operation with minimal security risk.

From the tool's definition Tool name 'device_get_target' and description 'Get current active platform and status' indicate retrieval of device state information with no modification or side effects.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

device_get_target Allowed

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

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

FAQ

Questions about device_get_target

What does the device_get_target tool do? +

Get current active platform and status. It is categorised as a Read tool in the Claude Mobile MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on device_get_target? +

Register the Claude Mobile MCP server in PolicyLayer and add a rule for device_get_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_get_target? +

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

Can I rate-limit device_get_target? +

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

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

device_get_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

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

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