Low Risk

get_tasks_by_priority

get_tasks_by_priority

How to control get_tasks_by_priority ↓

What get_tasks_by_priority does on Ticktick

AI agents call get_tasks_by_priority 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_by_priority needs a policy

This tool retrieves tasks filtered by priority level. It has no parameters that would modify, delete, or execute operations on the task system. The naming convention ('get_*') and context within a task management system strongly indicate a data retrieval operation with no side effects, making it Read category with low severity.

From the tool's definition Tool name 'get_tasks_by_priority' indicates a query/retrieval operation. The empty description provides no contradictory information.

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

How to control get_tasks_by_priority

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_by_priority:

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

get_tasks_by_priority 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_by_priority

What does the get_tasks_by_priority tool do? +

get_tasks_by_priority. 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_by_priority? +

Register the Ticktick MCP server in PolicyLayer and add a rule for get_tasks_by_priority: 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_by_priority? +

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

Can I rate-limit get_tasks_by_priority? +

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

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

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