v2.0: Detect which terminals are waiting for user input. Identifies common prompt patterns (package name:, version:, (y/n) etc), and returns suggestions. AI should periodically call this tool to respond to interactive commands
AI agents call detect_interactions 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 reads/queries the state of terminals to identify interactive prompts awaiting input. It has no side effects itself—it only observes and reports terminal states with suggestions. The AI then uses other tools to act. Severity is low since misuse only reveals terminal state information.
From the tool's definition Detect which terminals are waiting for user input... returns suggestions
Attacks that exploit this kind of access
v2.0: Detect which terminals are waiting for user input. Identifies common prompt patterns (package name:, version:, (y/n) etc), and returns suggestions. AI should periodically call this tool to respond to interactive commands. 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 detect_interactions: 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.
detect_interactions 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 detect_interactions 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 detect_interactions. 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.
detect_interactions 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 →