List all Happy AI sessions. Returns session IDs, titles, paths, machines, and activity status.
AI agents call happy_list_sessions to retrieve information from Happy Server MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only query operation that retrieves and enumerates existing session metadata. It has no capability to modify, delete, create, or execute actions. The blast radius is minimal—misuse would only expose information about existing sessions, not cause harm to systems or data.
From the tool's definition Tool name is 'happy_list_sessions' and description states it 'List all Happy AI sessions' and 'Returns session IDs, titles, paths, machines, and activity status.' The verb 'list' and 'returns' indicate data retrieval with no modification, creation, deletion,…
Attacks that exploit this kind of access
List all Happy AI sessions. Returns session IDs, titles, paths, machines, and activity status. It is categorised as a Read tool in the Happy Server MCP MCP Server, which means it retrieves data without modifying state.
Register the Happy Server MCP server in PolicyLayer and add a rule for happy_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 Happy Server MCP. Nothing to install.
happy_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 happy_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 happy_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.
happy_list_sessions is provided by the Happy Server MCP server (zhigang1992/happy-server-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 →