List all active HT sessions.
AI agents call ht_list_sessions to retrieve information from HT MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool performs a pure read operation—it lists/enumerates active sessions with no side effects. No data is created, modified, deleted, or executed. This is a low-severity read operation since session metadata is typically non-sensitive operational information, though in sensitive environments disclosure of active sessions could enable reconnaissance.
From the tool's definition Tool name is 'ht_list_sessions' and description states 'List all active HT sessions.' This is a query operation that retrieves information about existing sessions without modifying, executing, or deleting anything.
Attacks that exploit this kind of access
List all active HT sessions. It is categorised as a Read tool in the HT MCP Server MCP Server, which means it retrieves data without modifying state.
Register the HT MCP Server MCP server in PolicyLayer and add a rule for ht_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 HT MCP Server. Nothing to install.
ht_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 ht_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 ht_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.
ht_list_sessions is provided by the HT MCP Server MCP server (memextech/headless-terminal-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 →