Get detailed information about a specific client
AI agents call client_info_detailed 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 information about a TeamSpeak client without modifying, creating, or deleting any data. It is a read-only operation that returns client metadata. The blast radius of misuse is minimal—an attacker could gather information about connected users but cannot directly harm the system or cause irreversible changes.
From the tool's definition Tool name 'client_info_detailed' and description 'Get detailed information about a specific client' indicate a query/retrieval operation with no side effects.
Documented attack patterns abuse exactly the kind of access client_info_detailed 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 client_info_detailed:
{
"version": "1",
"default": "deny",
"tools": {
"client_info_detailed": {}
}
}client_info_detailed 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.
Get detailed information about a specific client. 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 client_info_detailed: 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.
client_info_detailed 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 client_info_detailed 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 client_info_detailed. 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.
client_info_detailed 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.