AI agents invoke kick_client to trigger actions in TeamSpeak MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
Kicking a client forcibly disconnects them from a server or channel. This is an external operation with immediate effect on a connected user. While not permanently destructive (the user can reconnect), it is an administrative action that triggers an external operation affecting real users, placing it in the Execute category. The blast radius is high because an AI agent could misuse this to disrupt legitimate users.
From the tool's definition Kick a client from server or channel
Documented attack patterns abuse exactly the kind of access kick_client 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 kick_client:
{
"version": "1",
"default": "deny",
"tools": {
"kick_client": {
"limits": [
{
"counter": "kick_client_rate",
"window": "minute",
"max": 10,
"scope": "grant"
}
]
}
}
}kick_client stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.
Free to start. No card required.
Kick a client from server or channel. It is categorised as a Execute tool in the TeamSpeak MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the TeamSpeak MCP server in PolicyLayer and add a rule for kick_client: 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.
kick_client is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the kick_client 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 kick_client. 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.
kick_client 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.