This record as markdown: /tools/cbrown35-20i-mcp/suspend-package.md
What suspend_package does on 20i MCP Server
AI agents call suspend_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.
Why suspend_package is rated Critical
Suspending a hosting package effectively takes all associated services offline (websites, email, databases, etc.), which is a high-impact, potentially irreversible action without an explicit unsuspend step.
From the tool's definition "Suspend a hosting package" - suspending a hosting package disables services for that package, which is a significant disruptive action that takes down websites, email, and other hosted services
Attacks that exploit this kind of access
The rule that runs suspend_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 suspend_package, this is the rule to start with:
suspend_package is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect 20i MCP Server, apply this rule, and every suspend_package call is checked against it from then on.
Questions about suspend_package
Suspend a hosting package. 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.
Register the 20i MCP Server MCP server in PolicyLayer and add a rule for suspend_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.
suspend_package 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 suspend_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.
Set action: deny in the PolicyLayer policy for suspend_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.
suspend_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.
More on 20i MCP Server, and thousands of servers like it.
Across the catalogue