Get the current authenticated user profile
AI agents call get_current_user 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 is a read-only operation that fetches the authenticated user's profile information. It performs no writes, deletions, code execution, or financial transactions. It has minimal blast radius if misused by an AI agent, as it only exposes the current user's own profile data that the authenticated session already has access to.
From the tool's definition Tool name 'get_current_user' and description 'Get the current authenticated user profile' indicate retrieval of user data with no modification or side effects.
Documented attack patterns abuse exactly the kind of access get_current_user gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and Ticktick, and nothing reaches the server without passing your rules. This is the rule we recommend for get_current_user:
{
"version": "1",
"default": "deny",
"tools": {
"get_current_user": {}
}
}get_current_user 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 the current authenticated user profile. 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 get_current_user: 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.
get_current_user 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 get_current_user 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 get_current_user. 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.
get_current_user is provided by the Ticktick MCP server (@alexarevalo.ai/mcp-server-ticktick). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from Ticktick, 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.
16 Ticktick tools catalogued and risk-classified — across an index of 43,000+ MCP servers.