AI agents call ticktick_get_projects 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 retrieves and queries project metadata without modifying, deleting, or executing any operations. It is a straightforward data retrieval function that falls squarely into the Read category with low severity since it only exposes project names and metadata without the ability to modify or act upon tasks.
From the tool's definition Tool name contains 'get' and description states 'list all TickTick projects' and 'Returns an array' with 'No parameters required', indicating a retrieval operation with no side effects.
Attacks that exploit this kind of access
Use this to list all TickTick projects/lists. Returns an array of projects with id, name, and other metadata. No parameters required. 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 ticktick_get_projects: 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.
ticktick_get_projects 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 ticktick_get_projects 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 ticktick_get_projects. 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.
ticktick_get_projects is provided by the Ticktick MCP server (produckteavity/ticktick-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 →