New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

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.

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/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.

Questions about desktop_get_target_pid

What does the desktop_get_target_pid tool do? +

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.

How do I enforce a policy on desktop_get_target_pid? +

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.

What risk level is desktop_get_target_pid? +

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

Can I rate-limit desktop_get_target_pid? +

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.

How do I block desktop_get_target_pid completely? +

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.

What MCP server provides desktop_get_target_pid? +

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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of Claude Mobile's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.