AI agents use assign_client_to_group 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.
This tool creates and modifies access control assignments (adding/removing clients from groups), which affects who has what permissions on the server. While not destructive (the change is reversible), it is a Write operation because it durably modifies server state (group membership lists).
From the tool's definition Tool description states 'Add or remove a client from a server group' — this modifies group membership, which changes user permissions and access controls within the TeamSpeak server.
Documented attack patterns abuse exactly the kind of access assign_client_to_group 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 assign_client_to_group:
{
"version": "1",
"default": "deny",
"tools": {
"assign_client_to_group": {
"limits": [
{
"counter": "assign_client_to_group_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}assign_client_to_group 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.
Add or remove a client from a server group. 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 assign_client_to_group: 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.
assign_client_to_group 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 assign_client_to_group 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 assign_client_to_group. 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.
assign_client_to_group 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.