admin_archive_project

Operator moderation action — archive a single project (sets

Server Run402 kychee-com/run402
Category Destructive
Risk class Critical
Parameters 00 required

What admin_archive_project does on Run402

AI agents call admin_archive_project to permanently remove resources in Run402 — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why admin_archive_project needs a policy

Archiving a project is effectively a destructive, likely irreversible action that disables or removes the project from active use. As an operator/admin moderation action, misuse could impact an entire project and its users. The description is truncated, reducing confidence slightly, but 'archive' consistently implies a non-reversible or hard-to-reverse state change in infrastructure contexts.

From the tool's definition admin_archive_project — 'archive a single project (sets'... description is truncated but 'archive' indicates the project is taken offline/frozen; operator moderation action implies administrative irreversible state change

Risk signalsAdmin/system-level operation

Questions about admin_archive_project

What does the admin_archive_project tool do? +

Operator moderation action — archive a single project (sets. It is categorised as a Destructive tool in the Run402 MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on admin_archive_project? +

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

What risk level is admin_archive_project? +

admin_archive_project is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit admin_archive_project? +

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

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

admin_archive_project is provided by the Run402 MCP server (kychee-com/run402). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER 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 →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.