refresh-project-cache

THE RISK

Low Risk

Why refresh-project-cache needs a policy

This tool fetches/retrieves project data from the API and updates a local cache. It reads data from an external source with no modification to actual tasks or projects. Cache refresh is a read operation with minimal blast radius.

From the tool's definition Manually refresh the project cache from the API

Documented attack patterns abuse exactly the kind of access refresh-project-cache gives an agent:

POLICY

How to control refresh-project-cache

PolicyLayer is an MCP gateway — it sits between your AI agents and Dida, and nothing reaches the server without passing your rules. This is the rule we recommend for refresh-project-cache:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "refresh-project-cache": {}
  }
}

refresh-project-cache is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.

Create a free account and register Dida — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CAP THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Dida tools

Destructive batch-delete-tasks Permanently removes multiple tasks from TickTick in a single operation. This batch operati Destructive complete-task Marks a task as completed in TickTick. This tool automatically finds the project containin Destructive delete-project Delete a project Destructive delete-task Permanently removes a task from TickTick. You must provide both the task ID and the projec Write batch-move-tasks Moves multiple tasks between projects in a single operation. This batch operation is more Write batch-update-tasks Updates multiple tasks in TickTick with new attributes in a single API call. This batch op Write create-project Create a new project Write create-task Creates a new task in TickTick with specified attributes. You can set title, content, prio

All 18 Dida tools →

Read tools on other servers

M-Team MCP Server get_torrent_detail YouTube MCP Server search_channel Android Forensics ADB MCP Server parse_browser_history 0xarchive web3_challenge

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Data exfiltration → How read access becomes an exfiltration channel when chained with untrusted content.
MCP token cost → What connecting this server costs in context-window tokens on every request.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about refresh-project-cache

What does the refresh-project-cache tool do? +

Manually refresh the project cache from the API. It is categorised as a Read tool in the Dida MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on refresh-project-cache? +

Register the Dida MCP server in PolicyLayer and add a rule for refresh-project-cache: 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 Dida. Nothing to install.

What risk level is refresh-project-cache? +

refresh-project-cache is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit refresh-project-cache? +

Yes. Add a rate_limit block to the refresh-project-cache 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.

How do I block refresh-project-cache completely? +

Set action: deny in the PolicyLayer policy for refresh-project-cache. 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.

What MCP server provides refresh-project-cache? +

refresh-project-cache is provided by the Dida MCP server (zhongwencool/dida-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Dida tool call.

Start from Dida, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →