debug_list_sessions

List all active debug sessions.

Server Polybugger wilfoa/polybugger-mcp
Category Read
Risk class Low
Parameters 00 required

What debug_list_sessions does on Polybugger

AI agents call debug_list_sessions to retrieve information from Polybugger without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why debug_list_sessions needs a policy

This tool queries and returns information about existing debug sessions without creating, modifying, deleting, or executing anything. It is a read-only information disclosure operation with minimal security impact.

From the tool's definition Tool name is 'debug_list_sessions' and description states 'List all active debug sessions' — a pure retrieval operation with no side effects.

Questions about debug_list_sessions

What does the debug_list_sessions tool do? +

List all active debug sessions. It is categorised as a Read tool in the Polybugger MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on debug_list_sessions? +

Register the Polybugger MCP server in PolicyLayer and add a rule for debug_list_sessions: 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 Polybugger. Nothing to install.

What risk level is debug_list_sessions? +

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

Can I rate-limit debug_list_sessions? +

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

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

debug_list_sessions is provided by the Polybugger MCP server (wilfoa/polybugger-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.