生成每周总结 (合并项目目标和CSV目标) Args: force_refresh: 是否强制刷新缓存数据 (默认为 False) Returns: 每周总结数据
AI agents call generate_weekly_summary to retrieve information from TickTick MCP Service without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool reads and aggregates existing task/goal data to produce a summary report. The force_refresh parameter merely invalidates a cache to re-fetch data, not modify anything. No data is created, modified, deleted, or financially impacted. It is a read/query operation with low blast radius.
From the tool's definition 生成每周总结 (合并项目目标和CSV目标) — 'generates a weekly summary' by merging/aggregating existing project and goal data; force_refresh only refreshes cached data
Documented attack patterns abuse exactly the kind of access generate_weekly_summary gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and TickTick MCP Service, and nothing reaches the server without passing your rules. This is the rule we recommend for generate_weekly_summary:
{
"version": "1",
"default": "deny",
"tools": {
"generate_weekly_summary": {}
}
}generate_weekly_summary 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.
生成每周总结 (合并项目目标和CSV目标) Args: force_refresh: 是否强制刷新缓存数据 (默认为 False) Returns: 每周总结数据. It is categorised as a Read tool in the TickTick MCP Service MCP Server, which means it retrieves data without modifying state.
Register the TickTick MCP Service MCP server in PolicyLayer and add a rule for generate_weekly_summary: 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 Service. Nothing to install.
generate_weekly_summary 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 generate_weekly_summary 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 generate_weekly_summary. 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.
generate_weekly_summary is provided by the TickTick MCP Service MCP server (galaxyxieyu/didatodolist-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from TickTick MCP Service, 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.
28 TickTick MCP Service tools catalogued and risk-classified — across an index of 43,000+ MCP servers.