Create a new HT (headless terminal) session. Returns a session ID that can be used with other HT tools. Optionally enable web server for live terminal preview.
AI agents invoke ht_create_session to trigger actions in HT MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Creating a headless terminal session instantiates an execution environment capable of running arbitrary commands and shell operations. Combined with sibling tools like ht_execute_command and ht_send_keys, this session is a gateway to arbitrary code execution. Enabling a web server further expands the attack surface. The blast radius is high as it bootstraps a persistent execution context.
From the tool's definition Create a new HT (headless terminal) session... Optionally enable web server for live terminal preview
Attacks that exploit this kind of access
Create a new HT (headless terminal) session. Returns a session ID that can be used with other HT tools. Optionally enable web server for live terminal preview. It is categorised as a Execute tool in the HT MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the HT MCP Server MCP server in PolicyLayer and add a rule for ht_create_session: 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_create_session is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the ht_create_session 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_create_session. 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_create_session 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 →