AI agents use ticktick_checkin_habit to create or update resources in TickTick MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your TickTick MCP Server environment.
Check-in actions create new entries in habit tracking logs that can be undone or modified later. The operation has minimal blast radius—it only records a user's habit completion for a single day. No code execution, financial transactions, or data destruction occurs. This is a straightforward Write operation.
From the tool's definition The tool description states it will 'Check in a habit for today' — this modifies habit tracking state by recording a completion entry for the current day.
Documented attack patterns abuse exactly the kind of access ticktick_checkin_habit gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and TickTick MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for ticktick_checkin_habit:
{
"version": "1",
"default": "deny",
"tools": {
"ticktick_checkin_habit": {
"limits": [
{
"counter": "ticktick_checkin_habit_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}ticktick_checkin_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.
Free to start. No card required.
Check in a habit for today. It is categorised as a Write tool in the TickTick MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the TickTick MCP Server MCP server in PolicyLayer and add a rule for ticktick_checkin_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 TickTick MCP Server. Nothing to install.
ticktick_checkin_habit 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 ticktick_checkin_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.
Set action: deny in the PolicyLayer policy for ticktick_checkin_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.
ticktick_checkin_habit is provided by the TickTick MCP Server MCP server (liadgez/ticktick-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from TickTick MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
114 TickTick MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.