List all threads in target process
AI agents call list_threads to retrieve information from MCP Debug Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and displays thread information from a target process. It is purely observational with no side effects—it does not create, modify, delete, or execute anything. It falls squarely into the Read category. Severity is low because knowing thread information carries minimal risk; an attacker could use it for reconnaissance, but thread lists are typically visible through standard OS tools.
From the tool's definition Tool name 'list_threads' and description 'List all threads in target process' indicate a query/inspection operation that retrieves thread information without modifying process state or executing code.
Attacks that exploit this kind of access
List all threads in target process. It is categorised as a Read tool in the MCP Debug Server MCP Server, which means it retrieves data without modifying state.
Register the MCP Debug Server 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 Debug Server. 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 Debug Server MCP server (nickzer0/mcp-debugserver). 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 →