AI agents call list_sessions to retrieve information from PiloTY without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The 'list' verb combined with 'sessions' indicates a read-only operation that enumerates or retrieves information about active or available terminal sessions. No side effects are expected. While the description is empty (slightly lowering confidence), the naming convention and context from sibling tools strongly suggest this is an informational query.
From the tool's definition Tool name is 'list_sessions' with empty description. Based on sibling tools (create_session, clear_scrollback, configure_session, send_line, send_password, send_signal, send_text, snapshot_screen), this server manages terminal sessions.
Documented attack patterns abuse exactly the kind of access list_sessions gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and PiloTY, and nothing reaches the server without passing your rules. This is the rule we recommend for list_sessions:
{
"version": "1",
"default": "deny",
"tools": {
"list_sessions": {}
}
}list_sessions 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.
list_sessions. It is categorised as a Read tool in the PiloTY MCP Server, which means it retrieves data without modifying state.
Register the PiloTY MCP server in PolicyLayer and add a rule for list_sessions: 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 PiloTY. Nothing to install.
list_sessions 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 list_sessions 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 list_sessions. 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.
list_sessions is provided by the PiloTY MCP server (yiwenlu66/piloty). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 17 PiloTY tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
17 PiloTY tools catalogued and risk-classified — across an index of 42,500+ MCP servers.