AI agents use send_private_message 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 new data (a private message) in a reversible manner. While it could be misused to spam or harass users, it does not execute code, delete data, or move money. The medium severity reflects potential for abuse (spam, impersonation) but the operation remains reversible and is confined to communication rather than system control.
From the tool's definition Tool name 'send_private_message' and description 'Send a private message to a user' indicate creation of new message data. This is a write operation that modifies the chat/message state of the server.
Documented attack patterns abuse exactly the kind of access send_private_message 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 send_private_message:
{
"version": "1",
"default": "deny",
"tools": {
"send_private_message": {
"limits": [
{
"counter": "send_private_message_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}send_private_message 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.
Send a private message to a user. 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 send_private_message: 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.
send_private_message 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 send_private_message 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 send_private_message. 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.
send_private_message 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.