remove_stack_user_from_package

Remove a Stack user from a hosting package

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/remove-stack-user-from-package.md

What remove_stack_user_from_package does on 20i MCP Server

AI agents call remove_stack_user_from_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 remove_stack_user_from_package is rated Critical

Removing a user from a hosting package revokes their access and associated permissions. This action is typically not easily reversible (the user must be re-added manually), making it a destructive operation. Misuse by an AI agent could cause loss of access for legitimate users, with a high blast radius if done on a production hosting environment.

From the tool's definition 'Remove a Stack user from a hosting package' — the word 'remove' indicates an irreversible revocation of access

Questions about remove_stack_user_from_package

What does the remove_stack_user_from_package tool do? +

Remove a Stack user from 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.

How do I enforce a policy on remove_stack_user_from_package? +

Register the 20i MCP Server MCP server in PolicyLayer and add a rule for remove_stack_user_from_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 remove_stack_user_from_package? +

remove_stack_user_from_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 remove_stack_user_from_package? +

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

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

remove_stack_user_from_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.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of 20i MCP Server's. Pull the full record:

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.