AI agents call get_terminal_info to retrieve information from MCP Terminal without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Despite being on a 'MCP Terminal' server with sibling tools like 'execute_command' that perform destructive operations, this specific tool is explicitly designed to retrieve information about the terminal itself rather than execute commands or modify state. Retrieving terminal metadata is a read-only operation with no side effects.
From the tool's definition Tool name 'get_terminal_info' combined with description 'Gets terminal information' indicates a retrieval operation.
Documented attack patterns abuse exactly the kind of access get_terminal_info gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and MCP Terminal, and nothing reaches the server without passing your rules. This is the rule we recommend for get_terminal_info:
{
"version": "1",
"default": "deny",
"tools": {
"get_terminal_info": {}
}
}get_terminal_info 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.
Gets terminal information. It is categorised as a Read tool in the MCP Terminal MCP Server, which means it retrieves data without modifying state.
Register the MCP Terminal MCP server in PolicyLayer and add a rule for get_terminal_info: 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 MCP Terminal. Nothing to install.
get_terminal_info 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_info 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_info. 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_info is provided by the MCP Terminal MCP server (sichang824/mcp-terminal). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from MCP Terminal, 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.
3 MCP Terminal tools catalogued and risk-classified — across an index of 43,000+ MCP servers.