Archive tasks to clean up communication directory (clear comms)
AI agents call archive_tasks to permanently remove resources in Agent Communication MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Archiving with a 'clear comms' intent suggests task data is removed from the active directory, which is likely irreversible. If tasks are permanently deleted or moved in a way that cannot be undone, this qualifies as Destructive. The 'clean up' phrasing strongly implies data is wiped rather than simply reorganized, making misuse potentially catastrophic for ongoing multi-agent workflows.
From the tool's definition 'Archive tasks to clean up communication directory (clear comms)' — 'clean up' and 'clear comms' imply irreversible removal or purging of task data from the communication directory
Attacks that exploit this kind of access
Archive tasks to clean up communication directory (clear comms). It is categorised as a Destructive tool in the Agent Communication MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Agent Communication MCP Server MCP server in PolicyLayer and add a rule for archive_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.
archive_tasks is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the archive_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.
Set action: deny in the PolicyLayer policy for archive_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.
archive_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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →