AI agents use usergroups_disable to create or update resources in Slack — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Slack environment.
Disabling a usergroup is a Write operation because it modifies organizational data (usergroup status) reversibly—the group can be re-enabled. It is not Destructive because the underlying data structure persists. Severity is high because disabling a usergroup can disrupt team communication and workflow by removing access permissions and notification routing for potentially many users, though the impact is recoverable.
From the tool's definition Tool name 'usergroups_disable' indicates modification of usergroup state. The Slack API family 'usergroups' manages user groups (collections of users); 'disable' is a state-change operation that deactivates a usergroup but does not permanently delete it,…
Attacks that exploit this kind of access
usergroups_disable. It is categorised as a Write tool in the Slack MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Slack MCP server in PolicyLayer and add a rule for usergroups_disable: 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.
usergroups_disable is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the usergroups_disable 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 usergroups_disable. 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.
usergroups_disable 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →