Low Risk

get_tasks_due_tomorrow

Get all tasks from TickTick that are due today. Ignores closed projects.

How to control get_tasks_due_tomorrow ↓

What get_tasks_due_tomorrow does on Ticktick

AI agents call get_tasks_due_tomorrow to retrieve information from Ticktick without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Low Risk

Why get_tasks_due_tomorrow needs a policy

This tool performs a simple read operation to retrieve tasks meeting a date criterion. There is no data creation, modification, deletion, or execution of commands. The blast radius of misuse is minimal—an AI agent retrieving task data poses no financial, destructive, or operational risk.

From the tool's definition Tool name is 'get_tasks_due_tomorrow' and description states 'Get all tasks from TickTick that are due today. Ignores closed projects.' This retrieves/queries task data with no modifications, deletions, or side effects.

Documented attack patterns abuse exactly the kind of access get_tasks_due_tomorrow gives an agent:

How to control get_tasks_due_tomorrow

PolicyLayer is an MCP gateway — it sits between your AI agents and Ticktick, and nothing reaches the server without passing your rules. This is the rule we recommend for get_tasks_due_tomorrow:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "get_tasks_due_tomorrow": {}
  }
}

get_tasks_due_tomorrow is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

  1. Create a free account and register Ticktick — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CAP THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about get_tasks_due_tomorrow

What does the get_tasks_due_tomorrow tool do? +

Get all tasks from TickTick that are due today. Ignores closed projects. It is categorised as a Read tool in the Ticktick MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on get_tasks_due_tomorrow? +

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

What risk level is get_tasks_due_tomorrow? +

get_tasks_due_tomorrow is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit get_tasks_due_tomorrow? +

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

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

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

Enforce policy on every Ticktick tool call.

Start from Ticktick, 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.

22 Ticktick tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.