Get focus session history.
AI agents call ticktick_get_focus_records 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 retrieves focus session history from TickTick, which is a read-only query operation. It accesses existing data without creating, modifying, deleting, or executing any actions. The blast radius of misuse is minimal—an AI agent could only view a user's focus session records, which is metadata about work sessions rather than sensitive financial or operational data. This clearly falls under the Read category.
From the tool's definition Tool name 'ticktick_get_focus_records' and description 'Get focus session history' indicate retrieval of historical data with no modification or side effects.
Attacks that exploit this kind of access
Get focus session history. 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_focus_records: 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_focus_records 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_focus_records 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_focus_records. 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_focus_records 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 →