ticktick_schedule_time · TickTick MCP Server MCP

WHAT IT DOES

What ticktick_schedule_time does on TickTick MCP Server

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

WHY IT NEEDS A POLICY

Why ticktick_schedule_time needs a policy

The tool name 'schedule_time' paired with the server's stated support for 'smart daily scheduling' suggests this tool modifies when tasks are scheduled—a reversible data modification operation. This falls under Write category. Severity is medium because scheduling changes could affect user productivity but are not irreversible (can be rescheduled) and do not involve destructive operations or financial impact.

From the tool's definition Tool name 'ticktick_schedule_time' combined with server's described capability of 'smart daily scheduling based on priorities and due dates' and sibling tools including 'ticktick_complete_task', 'ticktick_batch_create_tasks', and 'ticktick_configure' indicate…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

ticktick_schedule_time Rate-limited

ticktick_schedule_time 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": {
    "ticktick_schedule_time": {
      "limits": [
        {
          "counter": "ticktick_schedule_time_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 TickTick MCP Server, so you can run agents against it safely.

FAQ

Questions about ticktick_schedule_time

What does the ticktick_schedule_time tool do? +

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

How do I enforce a policy on ticktick_schedule_time? +

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

What risk level is ticktick_schedule_time? +

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

Can I rate-limit ticktick_schedule_time? +

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

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

ticktick_schedule_time is provided by the TickTick MCP Server MCP server (mostafasuliman/ticktick-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.