AI agents call ticktick_get_calendar_events 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.
This tool queries and returns calendar event data with no side effects. It falls squarely into the Read category (retrieves data; no side effects). The severity is low because listing calendar events poses minimal risk — it cannot modify, delete, or execute operations, and has no financial implications. Confidence is high given the clear read-only semantics in both name and description.
From the tool's definition Tool name is 'ticktick_get_calendar_events' and description states 'List calendar events' — both indicate a read-only operation that retrieves data without modification.
Documented attack patterns abuse exactly the kind of access ticktick_get_calendar_events 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_get_calendar_events:
{
"version": "1",
"default": "deny",
"tools": {
"ticktick_get_calendar_events": {}
}
}ticktick_get_calendar_events 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.
List calendar events. 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_get_calendar_events: 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_get_calendar_events 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_calendar_events 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_calendar_events. 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_calendar_events 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.