List all active touch sessions.
AI agents call touch_list_sessions to retrieve information from Mcp Remotetouch without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool queries and retrieves information about active touch sessions. It is a read-only operation that does not modify, execute, or destroy data. While the broader server enables remote control via SSH, this specific tool merely lists existing sessions without taking action on them. The low severity reflects minimal blast radius—an agent listing sessions cannot directly cause harm to the target system.
From the tool's definition Tool name 'touch_list_sessions' and description 'List all active touch sessions' indicate a query/retrieval operation with no modifications or side effects.
Attacks that exploit this kind of access
List all active touch sessions. It is categorised as a Read tool in the Mcp Remotetouch MCP Server, which means it retrieves data without modifying state.
Register the Mcp Remotetouch MCP server in PolicyLayer and add a rule for touch_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 Mcp Remotetouch. Nothing to install.
touch_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 touch_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 touch_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.
touch_list_sessions is provided by the Mcp Remotetouch MCP server (signal-slot/mcp-remotetouch). 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 →