archive_deployment

SERVERPortkey Admin SOURCEcodeswhat/portkey-admin-mcp

Critical RISK CLASS

Category Destructive

Parameters 00 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/codeswhat-portkey-admin-mcp/archive-deployment.md

WHAT IT DOES

What archive_deployment does on Portkey Admin

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

RISK

Why archive_deployment is rated Critical

Archiving a deployment deactivates it irreversibly, stopping active operations even if history persists.

From the tool's definition Archive a registered Gateway deployment...soft-deletes the record

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs archive_deployment safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Portkey Admin, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For archive_deployment, this is the rule to start with:

archive_deployment Hidden

archive_deployment is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "archive_deployment"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Portkey Admin, apply this rule, and every archive_deployment call is checked against it from then on.

FAQ

Questions about archive_deployment

What does the archive_deployment tool do? +

Enterprise-gated. Archive a registered Gateway deployment by UUID. Use get_deployment first to confirm the target. Portkey soft-deletes the record; this stops treating it as active but does not permanently remove its history. It is categorised as a Destructive tool in the Portkey Admin 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 archive_deployment? +

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

What risk level is archive_deployment? +

archive_deployment 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 archive_deployment? +

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

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

archive_deployment is provided by the Portkey Admin MCP server (codeswhat/portkey-admin-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Portkey Admin, and thousands of servers like it.

This server

All 170 Portkey Admin tools → Critical-risk tools on this server →

Across the catalogue

archive_purge on Templonix Lite MCP Server → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →