deactivate_package

Deactivate a hosting package to suspend services

SERVER20i MCP Server SOURCEcbrown35/20i-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/cbrown35-20i-mcp/deactivate-package.md

WHAT IT DOES

What deactivate_package does on 20i MCP Server

AI agents call deactivate_package to permanently remove resources in 20i MCP Server, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

RISK

Why deactivate_package is rated Critical

Deactivating a hosting package suspends all associated services (websites, email, databases, etc.) for that package. While technically 'reactivation' may be possible, the immediate effect is a broad service outage with high blast radius — all hosted services go offline. This is more severe than a simple Write operation and aligns with Destructive given the irreversible disruption to live services.

From the tool's definition 'Deactivate a hosting package to suspend services' - suspending services is an irreversible or impactful action that disrupts all services associated with the hosting package

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs deactivate_package safely

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

deactivate_package Hidden

deactivate_package 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": [
    "deactivate_package"
  ]
}

RESTRICT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect 20i MCP Server, apply this rule, and every deactivate_package call is checked against it from then on.

FAQ

Questions about deactivate_package

What does the deactivate_package tool do? +

Deactivate a hosting package to suspend services. It is categorised as a Destructive tool in the 20i MCP Server 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 deactivate_package? +

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

What risk level is deactivate_package? +

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

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

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

deactivate_package is provided by the 20i MCP Server MCP server (cbrown35/20i-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on 20i MCP Server, and thousands of servers like it.

This server

All 302 20i MCP Server tools → Critical-risk tools on this server →

Across the catalogue

All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →