List all threads in the debugged process
AI agents call list_threads to retrieve information from Mcp Debugger without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and returns thread information from an already-attached debugged process. It has no side effects, does not execute code, does not modify state, and does not delete or move data. It is a read-only inspection capability typical of debuggers, making it the lowest-risk category.
From the tool's definition Tool name is 'list_threads' and description states 'List all threads in the debugged process' — a purely informational query with no modification or execution of external operations.
Attacks that exploit this kind of access
List all threads in the debugged process. It is categorised as a Read tool in the Mcp Debugger MCP Server, which means it retrieves data without modifying state.
Register the Mcp Debugger MCP server in PolicyLayer and add a rule for list_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 Mcp Debugger. Nothing to install.
list_threads 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 list_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.
Set action: deny in the PolicyLayer policy for list_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.
list_threads is provided by the Mcp Debugger MCP server (@debugmcp/mcp-debugger). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →