AI agents call ticktick_export_project to retrieve information from TickTick MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Exporting project data is a read operation — it retrieves and packages existing data without modifying or deleting anything. The description 'Export project data' implies reading/querying project contents. Severity is low as misuse only exposes data that already exists in the project.
From the tool's definition Export project data
Documented attack patterns abuse exactly the kind of access ticktick_export_project gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and TickTick MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for ticktick_export_project:
{
"version": "1",
"default": "deny",
"tools": {
"ticktick_export_project": {}
}
}ticktick_export_project 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.
Export project data. It is categorised as a Read tool in the TickTick MCP Server MCP Server, which means it retrieves data without modifying state.
Register the TickTick MCP Server MCP server in PolicyLayer and add a rule for ticktick_export_project: 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 MCP Server. Nothing to install.
ticktick_export_project 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_export_project 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_export_project. 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_export_project is provided by the TickTick MCP Server MCP server (liadgez/ticktick-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from TickTick MCP Server, 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.
114 TickTick MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.