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

desktop

Desktop app management: launch (Gradle/bundle/attach), stop, windows, focus, resize, clipboard, performance, monitors, get_target_pid

SERVERClaude Mobile SOURCEalexgladkov/claude-in-mobile
High RISK CLASS
Category Execute
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/desktop.md

What desktop does on Claude Mobile

AI agents invoke desktop to trigger actions in Claude Mobile. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.

Why desktop is rated High

This tool performs multiple active operations on desktop applications: launching apps via Gradle/bundle/attach, stopping processes, manipulating windows (focus, resize), accessing clipboard data, and retrieving process IDs. These are external system operations with side effects including process execution, window management, and clipboard access.

From the tool's definition launch (Gradle/bundle/attach), stop, windows, focus, resize, clipboard, performance, monitors, get_target_pid

Questions about desktop

What does the desktop tool do? +

Desktop app management: launch (Gradle/bundle/attach), stop, windows, focus, resize, clipboard, performance, monitors, get_target_pid. It is categorised as a Execute tool in the Claude Mobile MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on desktop? +

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

desktop is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit desktop? +

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

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

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