AI agents use usergroups_enable 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.
The tool name suggests it activates or re-enables a user group in Slack, which is a reversible modification operation. This qualifies as Write rather than Execute because it appears to be a direct state-change action on a resource (user group) rather than arbitrary code execution. The severity is high because misuse could alter access controls and group membership visibility across an organization's Slack workspace.
From the tool's definition Tool name 'usergroups_enable' indicates it performs an action that modifies state (enabling a user group), not merely querying data. The empty description prevents confirmation of exact behavior, but 'enable' implies a state change operation.
Attacks that exploit this kind of access
usergroups_enable. 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_enable: 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_enable 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_enable 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_enable. 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_enable 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 →