Login with username/password for v2 API access.
AI agents invoke ticktick_login to trigger actions in TickTick MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool authenticates a session using credentials, triggering an external authentication operation with side effects (establishing a session/token). It's not a simple read, but rather an action that initiates external state (a live authenticated session). Not destructive or financial, but it executes an external operation whose effects depend on the provided credentials.
From the tool's definition Login with username/password for v2 API access
Attacks that exploit this kind of access
Login with username/password for v2 API access. It is categorised as a Execute tool in the TickTick MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the TickTick MCP Server MCP server in PolicyLayer and add a rule for ticktick_login: 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_login is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the ticktick_login 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_login. 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_login is provided by the TickTick MCP Server MCP server (mostafasuliman/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 →