Get a task by ProjectId and TaskId
AI agents call get_task_by_ids 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.
This tool queries and retrieves task information based on identifiers. It performs a read-only operation with no capability to modify, delete, or execute actions. The blast radius is minimal—an AI agent using this tool can only view existing task data, which poses no security risk beyond potential information disclosure depending on task content sensitivity.
From the tool's definition Tool name 'get_task_by_ids' and description 'Get a task by ProjectId and TaskId' indicate retrieval of task data without modification or side effects.
Documented attack patterns abuse exactly the kind of access get_task_by_ids 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_task_by_ids:
{
"version": "1",
"default": "deny",
"tools": {
"get_task_by_ids": {}
}
}get_task_by_ids 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 a task by ProjectId and TaskId. 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_task_by_ids: 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_task_by_ids 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_task_by_ids 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_task_by_ids. 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_task_by_ids is provided by the Ticktick MCP server (@alexarevalo.ai/mcp-server-ticktick). 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.
16 Ticktick tools catalogued and risk-classified — across an index of 43,000+ MCP servers.