`peaka_post__data_projects_projectId_cache_cacheId_cancelFullRefreshUpdate` – 1 MCP server offers this tool

What it usually takes

No server marks it as only reading: treat it as able to change data.

From each publisher's own tool list. We never call a tool.

Server	Inputs	Read-only?
Peaka `co.huggingface.ramamatar/peaka` Cancels a currently running full refresh (resync) workflow for the specified cache. This sends a cancellation signal to the underlying Temporal workflow. The cancellation is best-effort: if the workflow has already completed or is in its final stages, the cancel request may have no effect. Only workflows with a RUNNING status can be cancelled. After successful cancellation, the cache status transitions to CANCELLED. The previously cached data remains intact (the partial refresh data is discarded). A new full refresh or incremental sync can be triggered after cancellation. This endpoint only affects the full refresh workflow. To cancel an incremental sync, use the Cancel Incremental Update endpoint instead.	`cacheId`,`projectId`	Not stated