List all active terminal sessions (running processes).
AI agents call list_sessions to retrieve information from TermPipe MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool retrieves information about running processes and active sessions without creating, modifying, deleting, or executing operations. It is a read-only operation with minimal security impact—an AI agent querying this information could learn about system state but cannot directly harm systems or data. Severity is low because exposure is limited to metadata visibility.
From the tool's definition Tool name is 'list_sessions' and description states it 'List[s] all active terminal sessions (running processes).' This is a query operation with no modifications.
Attacks that exploit this kind of access
List all active terminal sessions (running processes). It is categorised as a Read tool in the TermPipe MCP MCP Server, which means it retrieves data without modifying state.
Register the TermPipe 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 TermPipe MCP. 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 TermPipe MCP server (wbind-core/termpipe-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 →