remove_stack_user_from_package
Remove a Stack user from a hosting package
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
Attacks that exploit this kind of access
The rule that runs remove_stack_user_from_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 remove_stack_user_from_package, this is the rule to start with:
remove_stack_user_from_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 remove_stack_user_from_package call is checked against it from then on.
Questions about remove_stack_user_from_package
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.
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.
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.
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.
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.
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.
Across the catalogue