List all machines registered with Happy. Returns machine IDs, hostnames, platforms, and activity status.
AI agents call happy_list_machines 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 retrieves and queries information about registered machines without modifying, executing code on, deleting, or creating any resources. It is a pure read operation that returns metadata about machines in the system.
From the tool's definition Tool name 'happy_list_machines' and description 'List all machines registered with Happy. Returns machine IDs, hostnames, platforms, and activity status' indicate data retrieval with no side effects.
Attacks that exploit this kind of access
List all machines registered with Happy. Returns machine IDs, hostnames, platforms, 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_machines: 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_machines 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_machines 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_machines. 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_machines 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 →