AI agents call list_complaints to retrieve information from TeamSpeak MCP without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves or queries complaint data from the TeamSpeak server without creating, modifying, deleting, or executing any actions. It is a simple read operation that returns existing information. The blast radius of misuse is minimal since no state changes occur and the data returned is informational about existing complaints.
From the tool's definition Tool name is 'list_complaints' and description states 'List complaints on the virtual server'. The verb 'list' indicates a retrieval operation with no modification or deletion of data.
Documented attack patterns abuse exactly the kind of access list_complaints 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 list_complaints:
{
"version": "1",
"default": "deny",
"tools": {
"list_complaints": {}
}
}list_complaints is read-only, so it stays allowed — but everything else on the server is denied unless you say otherwise.
Free to start. No card required.
List complaints on the virtual server. It is categorised as a Read tool in the TeamSpeak MCP MCP Server, which means it retrieves data without modifying state.
Register the TeamSpeak MCP server in PolicyLayer and add a rule for list_complaints: 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.
list_complaints is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the list_complaints 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 list_complaints. 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.
list_complaints 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.