v2.0: Get detailed states of all terminals, core tool for AI task scheduling. Returns each terminal
AI agents call get_terminal_states to retrieve information from Ai Mcp Terminal without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and returns information about terminal states without executing commands, modifying data, or causing side effects. It is purely informational and used for monitoring/scheduling purposes. The read-only nature and lack of side effects classify it as a Read operation with low severity.
From the tool's definition Tool name 'get_terminal_states' and description 'Get detailed states of all terminals' indicate a retrieval operation with no modification or execution of commands. Returns terminal state information only.
Attacks that exploit this kind of access
v2.0: Get detailed states of all terminals, core tool for AI task scheduling. Returns each terminal. It is categorised as a Read tool in the Ai Mcp Terminal MCP Server, which means it retrieves data without modifying state.
Register the Ai Mcp Terminal MCP server in PolicyLayer and add a rule for get_terminal_states: 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 Ai Mcp Terminal. Nothing to install.
get_terminal_states 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 get_terminal_states 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 get_terminal_states. 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.
get_terminal_states is provided by the Ai Mcp Terminal MCP server (kanniganfan/ai-mcp-terminal). 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 →