AI agents use create_channel to create or update resources in TeamSpeak MCP — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your TeamSpeak MCP environment.
Creating a channel is a reversible modification to server state—the channel can be deleted afterward. This is a Write operation, not Destructive (deletion is irreversible) or Execute (which would apply to code execution or triggering external processes). Severity is medium because an AI agent could create many channels, consuming resources or disrupting server organization, but the impact is bounded and reversible.
From the tool's definition Tool description states 'Create a new channel', which is a create operation that modifies server state by adding a new channel.
Documented attack patterns abuse exactly the kind of access create_channel gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and TeamSpeak MCP, and nothing reaches the server without passing your rules. This is the rule we recommend for create_channel:
{
"version": "1",
"default": "deny",
"tools": {
"create_channel": {
"limits": [
{
"counter": "create_channel_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}create_channel stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Create a new channel. It is categorised as a Write tool in the TeamSpeak MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the TeamSpeak 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 TeamSpeak MCP. 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 TeamSpeak MCP server (marlburrow/teamspeak-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Start from TeamSpeak MCP, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.
Free to start. No card required.
40 TeamSpeak MCP tools catalogued and risk-classified — across an index of 43,000+ MCP servers.