AI agents call list_debug_sessions to retrieve information from Pwno 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 information about existing debug sessions without modifying, deleting, or executing any operations. It is a pure read operation that gathers metadata about the state of the debugging system. The low severity reflects minimal risk even if misused by an agent, as listing sessions causes no harm.
From the tool's definition Tool name 'list_debug_sessions' and description 'List all active debug sessions and metadata' indicates a query/retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access list_debug_sessions gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Pwno, and nothing reaches the server without passing your rules. This is the rule we recommend for list_debug_sessions:
{
"version": "1",
"default": "deny",
"tools": {
"list_debug_sessions": {}
}
}list_debug_sessions is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List all active debug sessions and metadata. It is categorised as a Read tool in the Pwno MCP Server, which means it retrieves data without modifying state.
Register the Pwno MCP server in PolicyLayer and add a rule for list_debug_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 Pwno. Nothing to install.
list_debug_sessions 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_debug_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.
Set action: deny in the PolicyLayer policy for list_debug_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.
list_debug_sessions is provided by the Pwno MCP server (pwno-io/pwno-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 36 Pwno tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
36 Pwno tools catalogued and risk-classified — across an index of 42,500+ MCP servers.