debug_threads

List threads of the debugged VM with ids and names (Android). Use an id with debug_pause_state / debug_step to target a specific thread.

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/debug-threads.md

WHAT IT DOES

What debug_threads does on Claude Mobile

AI agents call debug_threads 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 debug_threads is rated Low

Read-only operation that retrieves thread information without modifying state.

From the tool's definition List threads of the debugged VM with ids and names

Attacks that exploit this kind of access

RECOMMENDED RULE

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

debug_threads Allowed

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

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

FAQ

Questions about debug_threads

What does the debug_threads tool do? +

List threads of the debugged VM with ids and names (Android). Use an id with debug_pause_state / debug_step to target a specific thread. 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 debug_threads? +

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

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

Can I rate-limit debug_threads? +

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

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

debug_threads 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

The MCP Attack Database →

Guides

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