update_habit · Tick MCP: Risk & Policy

WHAT IT DOES

What update_habit does on Tick

AI agents use update_habit to create or update resources in Tick — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Tick environment.

WHY IT NEEDS A POLICY

Why update_habit needs a policy

The 'update_' prefix indicates a Write operation that modifies existing habit data in TickTick. This is reversible (can be updated again or reverted) and non-destructive. Confidence is moderate (0.75) rather than high because the description is empty, leaving some ambiguity about exact behavior, though the naming pattern and server context strongly suggest a standard update operation.

From the tool's definition Tool name 'update_habit' with prefix 'update' indicates modification of existing data. The sibling tools on this server include 'batch_update_tasks' and 'create_habit', establishing the pattern that 'update_*' tools modify data reversibly.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_habit Rate-limited

update_habit 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": {
    "update_habit": {
      "limits": [
        {
          "counter": "update_habit_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 Tick, so you can run agents against it safely.

FAQ

Questions about update_habit

What does the update_habit tool do? +

update_habit. It is categorised as a Write tool in the Tick MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_habit? +

Register the Tick MCP server in PolicyLayer and add a rule for update_habit: 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 Tick. Nothing to install.

What risk level is update_habit? +

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

Can I rate-limit update_habit? +

Yes. Add a rate_limit block to the update_habit 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 update_habit completely? +

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

update_habit is provided by the Tick MCP server (kpihx/tick-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.