AI agents call ban_client to permanently remove resources in TeamSpeak MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Banning a client from a TeamSpeak server denies them access, which is a significant and difficult-to-reverse administrative action. Unlike a temporary mute or kick, a ban persists and requires deliberate action to undo. Misuse by an AI agent could result in legitimate users being permanently locked out of the server.
From the tool's definition 'Ban a client from the server' — banning removes a user's access and is typically irreversible or semi-permanent, constituting a destructive administrative action.
Documented attack patterns abuse exactly the kind of access ban_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 ban_client:
{
"version": "1",
"default": "deny",
"hide": [
"ban_client"
]
}ban_client disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.
Free to start. No card required.
Ban a client from the server. It is categorised as a Destructive tool in the TeamSpeak MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the TeamSpeak MCP server in PolicyLayer and add a rule for ban_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.
ban_client is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the ban_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 ban_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.
ban_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.