Get current notification preferences and settings
AI agents call ticktick_get_notification_settings 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 retrieves the user's notification settings without creating, modifying, or deleting any data. It is a read-only operation that poses minimal risk if misused by an AI agent, as the worst outcome is exposure of the user's own notification preferences.
From the tool's definition Tool name includes 'get' and description states 'Get current notification preferences and settings' — a pure retrieval operation with no modifications, deletions, or side effects.
Documented attack patterns abuse exactly the kind of access ticktick_get_notification_settings 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_notification_settings:
{
"version": "1",
"default": "deny",
"tools": {
"ticktick_get_notification_settings": {}
}
}ticktick_get_notification_settings 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 current notification preferences and settings. 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_notification_settings: 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_notification_settings 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_notification_settings 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_notification_settings. 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_notification_settings 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.