AI agents call list_terminal_sessions to retrieve information from Interactive Automation MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name 'list' strongly indicates a query/retrieval operation with no side effects. While the description is empty, the naming convention and server context (which includes other Read tools like get_screen_content) support classification as a simple enumeration of existing sessions. This is lower confidence due to missing description, but the semantic meaning is clear.
From the tool's definition Tool name 'list_terminal_sessions' combined with server context describing expect/pexpect-style automation indicates this retrieves information about existing terminal sessions.
Documented attack patterns abuse exactly the kind of access list_terminal_sessions gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Interactive Automation MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for list_terminal_sessions:
{
"version": "1",
"default": "deny",
"tools": {
"list_terminal_sessions": {}
}
}list_terminal_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_terminal_sessions. It is categorised as a Read tool in the Interactive Automation MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Interactive Automation MCP Server MCP server in PolicyLayer and add a rule for list_terminal_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 Interactive Automation MCP Server. Nothing to install.
list_terminal_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_terminal_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_terminal_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_terminal_sessions is provided by the Interactive Automation MCP Server MCP server (wehnsdaefflae/terminal-control-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Interactive Automation MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
6 Interactive Automation MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.