Create a new Slack channel.
AI agents use create_channel to create or update resources in Slack MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Slack MCP Server environment.
Creating a channel is a write operation that adds new data to the workspace. It is reversible (channels can be archived or deleted), so it does not qualify as Destructive. The severity is medium because while workspace-wide, channel creation has limited blast radius compared to destructive operations—unintended channels can be easily removed and do not expose sensitive data or cause financial impact.
From the tool's definition Tool name is 'create_channel' and description states 'Create a new Slack channel.' This creates a new resource in the Slack workspace.
Attacks that exploit this kind of access
Create a new Slack channel. It is categorised as a Write tool in the Slack MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Slack MCP Server MCP server in PolicyLayer and add a rule for create_channel: 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 MCP Server. Nothing to install.
create_channel 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 create_channel 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 create_channel. 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.
create_channel is provided by the Slack MCP Server MCP server (piekstra/slack-mcp-server). 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 →