archive_completed_tasks · Agent Communication MCP Server MCP

WHAT IT DOES

What archive_completed_tasks does on Agent Communication MCP Server

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

WHY IT NEEDS A POLICY

Why archive_completed_tasks needs a policy

Archiving constitutes a reversible write operation that modifies task records by changing their status or location. While technically the data may still be recoverable, the tool irreversibly changes the visibility or accessibility state of completed tasks in the active system.

From the tool's definition Tool description states 'Archive all completed tasks - batch cleanup operation'. Archiving is a data modification operation that changes the state of multiple tasks (moves them to archived status) in a batch.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

archive_completed_tasks Rate-limited

archive_completed_tasks 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": {
    "archive_completed_tasks": {
      "limits": [
        {
          "counter": "archive_completed_tasks_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 Agent Communication MCP Server, so you can run agents against it safely.

FAQ

Questions about archive_completed_tasks

What does the archive_completed_tasks tool do? +

Archive all completed tasks - batch cleanup operation. It is categorised as a Write tool in the Agent Communication 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 archive_completed_tasks? +

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

What risk level is archive_completed_tasks? +

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

Can I rate-limit archive_completed_tasks? +

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

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

archive_completed_tasks is provided by the Agent Communication MCP Server MCP server (jerfowler/agent-comm-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.