AI agents call get_completed_tasks to retrieve information from Tick without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Despite the empty description, the tool name strongly suggests a read-only query operation that retrieves already-completed tasks from TickTick. No creation, modification, deletion, or execution of external actions is implied. The naming convention aligns with other sibling read operations on the server. Even if misused by an agent, retrieving completed task information carries minimal security risk.
From the tool's definition Tool name 'get_completed_tasks' indicates retrieval of existing task data with no modification capability. The verb 'get' is a standard read operation pattern.
Attacks that exploit this kind of access
get_completed_tasks. It is categorised as a Read tool in the Tick MCP Server, which means it retrieves data without modifying state.
Register the Tick MCP server in PolicyLayer and add a rule for get_completed_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 Tick. Nothing to install.
get_completed_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_completed_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_completed_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_completed_tasks is provided by the Tick MCP server (kpihx/tick-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →