Update a Zen (todo) item title and/or description.
AI agents use happy_zen_update_todo to create or update resources in Happy Server MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Happy Server MCP environment.
This tool modifies existing data (todo item metadata) in a reversible manner. It is not destructive (no deletion), does not execute code, does not create financial obligations, and does not read-only. The blast radius is minimal — a user could update todo items incorrectly, but this can be corrected by updating again. Categorized as Write.
From the tool's definition Tool name contains 'update' and description states 'Update a Zen (todo) item title and/or description' — classic data modification operation on todo items that is reversible.
Attacks that exploit this kind of access
Update a Zen (todo) item title and/or description. It is categorised as a Write tool in the Happy Server MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Happy Server MCP server in PolicyLayer and add a rule for happy_zen_update_todo: 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_update_todo is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the happy_zen_update_todo 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_update_todo. 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_update_todo 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 →