desktop_get_target_pid
Get the PID of the native app set by the last desktop_launch (bundle or attach mode). Returns null if no target PID is set.
This record as markdown: /tools/alexgladkov-claude-in-mobile/desktop-get-target-pid.md
What desktop_get_target_pid does on Claude Mobile
AI agents call desktop_get_target_pid 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.
Why desktop_get_target_pid is rated Low
This tool only queries and retrieves the PID (process identifier) of a native app that was previously launched. It performs no modification, execution, or deletion of data or processes. The operation is a simple read/query with no side effects, making it a Read category tool with low severity.
From the tool's definition Tool name includes 'get' and description states it 'Returns' a PID value with no modification of state. It retrieves information about a previously-set target process ID.
Attacks that exploit this kind of access
The rule that runs desktop_get_target_pid 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 desktop_get_target_pid, this is the rule to start with:
desktop_get_target_pid is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Claude Mobile, apply this rule, and every desktop_get_target_pid call is checked against it from then on.
Questions about desktop_get_target_pid
Get the PID of the native app set by the last desktop_launch (bundle or attach mode). Returns null if no target PID is set. It is categorised as a Read tool in the Claude Mobile MCP Server, which means it retrieves data without modifying state.
Register the Claude Mobile MCP server in PolicyLayer and add a rule for desktop_get_target_pid: 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.
desktop_get_target_pid is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the desktop_get_target_pid 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 desktop_get_target_pid. 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.
desktop_get_target_pid 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.
More on Claude Mobile, and thousands of servers like it.
This server
Across the catalogue