happy_zen_set_todo_done · Happy Server MCP: Risk & Policy

WHAT IT DOES

What happy_zen_set_todo_done does on Happy Server MCP

AI agents use happy_zen_set_todo_done 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.

WHY IT NEEDS A POLICY

Why happy_zen_set_todo_done needs a policy

This tool creates or modifies data (todo completion status) in a reversible manner. The operation can be undone by toggling the status back. It does not delete data (Destructive), execute arbitrary code (Execute), move money (Financial), or merely read (Read). It fits the Write category as a state modification tool.

From the tool's definition Tool name and description indicate it 'Set[s] or toggle[s] a Zen (todo) item completion status' — modifying the state of a todo item without deletion or irreversible destruction.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

happy_zen_set_todo_done Rate-limited

happy_zen_set_todo_done stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "happy_zen_set_todo_done": {
      "limits": [
        {
          "counter": "happy_zen_set_todo_done_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Happy Server MCP, so you can run agents against it safely.

FAQ

Questions about happy_zen_set_todo_done

What does the happy_zen_set_todo_done tool do? +

Set or toggle a Zen (todo) item completion status. 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.

How do I enforce a policy on happy_zen_set_todo_done? +

Register the Happy Server MCP server in PolicyLayer and add a rule for happy_zen_set_todo_done: 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.

What risk level is happy_zen_set_todo_done? +

happy_zen_set_todo_done is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit happy_zen_set_todo_done? +

Yes. Add a rate_limit block to the happy_zen_set_todo_done 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.

How do I block happy_zen_set_todo_done completely? +

Set action: deny in the PolicyLayer policy for happy_zen_set_todo_done. 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.

What MCP server provides happy_zen_set_todo_done? +

happy_zen_set_todo_done 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.