Archive or delete an activity
AI agents call archive_activity to permanently remove resources in EARLY App MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
The tool can delete an activity outright, which is irreversible. Even archiving is a one-way state change that removes the activity from normal workflows. Since the description includes 'delete', the most severe applicable category is Destructive. High severity because deleting activities could orphan or corrupt associated time entries and reports.
From the tool's definition "Archive or delete an activity" — the description explicitly mentions deletion, and archiving is typically irreversible or at minimum removes the activity from active use
Attacks that exploit this kind of access
Archive or delete an activity. It is categorised as a Destructive tool in the EARLY App MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the EARLY App MCP Server MCP server in PolicyLayer and add a rule for archive_activity: 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 EARLY App MCP Server. Nothing to install.
archive_activity 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_activity 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_activity. 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_activity is provided by the EARLY App MCP Server MCP server (janfincke/early-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 →