users_admin_set_inactive
Deactivate a user (legacy undocumented).
This record as markdown: /tools/karbassi-slack-mcp/users-admin-set-inactive.md
What users_admin_set_inactive does on Slack
AI agents call users_admin_set_inactive to permanently remove resources in Slack, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why users_admin_set_inactive is rated Critical
Deactivating a user account is a destructive, high-impact action that removes the user's access to Slack. While technically reversible by an admin, it constitutes an irreversible change from the user's perspective and can disrupt their work. The 'legacy undocumented' nature also raises concerns about unexpected side effects. Severity is high because misuse could lock out legitimate users.
From the tool's definition 'Deactivate a user' — deactivating a user account removes their access and is not easily reversible through standard workflows
Attacks that exploit this kind of access
The rule that runs users_admin_set_inactive safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Slack, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For users_admin_set_inactive, this is the rule to start with:
users_admin_set_inactive 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 Slack, apply this rule, and every users_admin_set_inactive call is checked against it from then on.
Questions about users_admin_set_inactive
Deactivate a user (legacy undocumented). It is categorised as a Destructive tool in the Slack MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Slack MCP server in PolicyLayer and add a rule for users_admin_set_inactive: 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 Slack. Nothing to install.
users_admin_set_inactive 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 users_admin_set_inactive 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 users_admin_set_inactive. 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.
users_admin_set_inactive is provided by the Slack MCP server (karbassi/slack-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Slack, and thousands of servers like it.
Across the catalogue