Get detailed statistics about a terminal session including size, tokens, etc.
AI agents call get_terminal_stats to retrieve information from Persistent Terminal MCP Server 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 an existing terminal session (size, tokens, etc.) with no side effects, state changes, or command execution. It is purely informational and aligns with the Read category pattern of data retrieval operations like 'get' and 'fetch'.
From the tool's definition Tool name 'get_terminal_stats' and description 'Get detailed statistics about a terminal session' indicate retrieval of session metadata without modification or execution.
Attacks that exploit this kind of access
Get detailed statistics about a terminal session including size, tokens, etc. It is categorised as a Read tool in the Persistent Terminal MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Persistent Terminal MCP Server MCP server in PolicyLayer and add a rule for get_terminal_stats: 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 Persistent Terminal MCP Server. Nothing to install.
get_terminal_stats 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_stats 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_stats. 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_stats is provided by the Persistent Terminal MCP Server MCP server (masx200/persistent-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 →