AI agents call get_next_tasks 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.
Despite having an empty description, the tool name and context from sibling tools indicate this retrieves upcoming/next tasks from the TickTick system. Retrieval operations have no side effects and fall under the Read category. Confidence is reduced slightly due to missing description, but the contextual evidence from related tools is strong.
From the tool's definition Tool name 'get_next_tasks' combined with sibling tools named 'get_all_tasks', 'get_engaged_tasks', and 'get_overdue_tasks' indicates this is a retrieval/query function. The naming pattern across the server strongly suggests data retrieval without modification.
Documented attack patterns abuse exactly the kind of access get_next_tasks gives an agent:
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_next_tasks:
{
"version": "1",
"default": "deny",
"tools": {
"get_next_tasks": {}
}
}get_next_tasks is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
get_next_tasks. It is categorised as a Read tool in the Ticktick MCP Server, which means it retrieves data without modifying state.
Register the Ticktick MCP server in PolicyLayer and add a rule for get_next_tasks: 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.
get_next_tasks is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the get_next_tasks 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 get_next_tasks. 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.
get_next_tasks 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.
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.