List all active debugging sessions: id, state, pid, architecture, executable, breakpointCount.
AI agents call list_sessions to retrieve information from x64dbg MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This is a Read operation: it retrieves information about running debug sessions without changing system state. However, severity is elevated to 'high' because the tool reveals sensitive runtime metadata (process IDs, architectures, loaded executables, and breakpoint counts) which an adversarial agent could leverage to map running processes, identify targets for further exploitation, or understand defensive…
From the tool's definition Tool lists active debugging sessions, returning session metadata (id, state, pid, architecture, executable, breakpointCount) with no modification or deletion. The name 'list_sessions' and description indicate a query-only operation with no side effects.
Attacks that exploit this kind of access
List all active debugging sessions: id, state, pid, architecture, executable, breakpointCount. It is categorised as a Read tool in the x64dbg MCP Server MCP Server, which means it retrieves data without modifying state.
Register the x64dbg MCP Server MCP server in PolicyLayer and add a rule for 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 x64dbg MCP Server. Nothing to install.
list_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_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_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_sessions is provided by the x64dbg MCP Server MCP server (ouonet/x64dbg-mcp). 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 →