List Zen (todo) items with titles, descriptions, and completion status.
AI agents call happy_zen_list_todos 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 queries and returns todo item metadata (titles, descriptions, completion status). It has no capacity to create, modify, delete, execute code, or trigger external operations. The read-only nature and absence of side effects classify it as a Read category risk with low severity.
From the tool's definition Tool name and description indicate retrieval operation: 'List Zen (todo) items with titles, descriptions, and completion status.' The verb 'list' is a canonical read operation that retrieves data without modification or side effects.
Attacks that exploit this kind of access
List Zen (todo) items with titles, descriptions, and completion 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_zen_list_todos: 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_zen_list_todos 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_zen_list_todos 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_zen_list_todos. 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_zen_list_todos 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 →