AI agents call list_pwncli_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 session metadata for informational purposes only. While the server as a whole provides debugging and exploit capabilities (which involve Execute-category tools), this specific tool merely enumerates active sessions. The blast radius of misuse is minimal—an agent could discover what sessions exist, but cannot directly modify system state, execute code, or cause financial harm through listing alone.
From the tool's definition The tool name 'list_pwncli_sessions' and description 'List all active pwncli driver sessions' indicate a read-only operation that queries and returns information about existing debugging sessions without modifying, executing, or deleting anything.
Documented attack patterns abuse exactly the kind of access list_pwncli_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_pwncli_sessions:
{
"version": "1",
"default": "deny",
"tools": {
"list_pwncli_sessions": {}
}
}list_pwncli_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 pwncli driver sessions. 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_pwncli_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_pwncli_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_pwncli_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_pwncli_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_pwncli_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.