terminal_get_sessions
AI agents call terminal_get_sessions to retrieve information from Electron Terminal MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'get' prefix strongly indicates a query or retrieval operation that would list or fetch terminal session information without causing side effects. While the empty description introduces some ambiguity, the natural interpretation is that this tool returns session data for inspection, which is a Read operation.
From the tool's definition Tool name is `terminal_get_sessions` with 'get' indicating a retrieval operation. Empty description limits certainty, but naming pattern and context (sibling tools include `terminal_start`, `terminal_stop`, `terminal_execute`) suggest this retrieves session…
Attacks that exploit this kind of access
terminal_get_sessions. It is categorised as a Read tool in the Electron Terminal MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Electron Terminal MCP Server MCP server in PolicyLayer and add a rule for terminal_get_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 Electron Terminal MCP Server. Nothing to install.
terminal_get_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 terminal_get_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 terminal_get_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.
terminal_get_sessions is provided by the Electron Terminal MCP Server MCP server (nexon33/console-terminal-mcp-server). 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 →