archiveDoneTasks · Knowledge MCP Server MCP: Risk & Policy

WHAT IT DOES

What archiveDoneTasks does on Knowledge MCP Server

AI agents use archiveDoneTasks to create or update resources in Knowledge MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Knowledge MCP Server environment.

WHY IT NEEDS A POLICY

Why archiveDoneTasks needs a policy

This tool creates and modifies markdown files (archiving completed tasks) and commits changes to git, which are reversible write operations. While it involves deletion from source files (today.md and backlog.md), the tasks are preserved in an archive file rather than irreversibly purged, so this is Write rather than Destructive.

From the tool's definition The tool "moves" (modifies) completed tasks from multiple files into an archive file, and explicitly "Returns count of archived tasks" and "All changes in one atomic git commit" indicating file modification and version control operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

archiveDoneTasks Rate-limited

archiveDoneTasks stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "archiveDoneTasks": {
      "limits": [
        {
          "counter": "archivedonetasks_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Knowledge MCP Server, so you can run agents against it safely.

FAQ

Questions about archiveDoneTasks

What does the archiveDoneTasks tool do? +

Move all completed [x] tasks from today.md and backlog.md into a monthly archive file (tasks/archive/YYYY-MM.md), grouped by date with timestamps. Returns count of archived tasks. All changes in one atomic git commit. Use this when the user says. It is categorised as a Write tool in the Knowledge MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on archiveDoneTasks? +

Register the Knowledge MCP Server MCP server in PolicyLayer and add a rule for archiveDoneTasks: 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 Knowledge MCP Server. Nothing to install.

What risk level is archiveDoneTasks? +

archiveDoneTasks is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit archiveDoneTasks? +

Yes. Add a rate_limit block to the archiveDoneTasks 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 archiveDoneTasks completely? +

Set action: deny in the PolicyLayer policy for archiveDoneTasks. 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 archiveDoneTasks? +

archiveDoneTasks is provided by the Knowledge MCP Server MCP server (vuluu2k/knowledge_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.