Get instance-level logs instead of virtual server logs
AI agents call get_instance_logs 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 log data for informational purposes only. Reading logs does not modify state, execute operations, or produce irreversible changes. Even in a server administration context, log retrieval is a passive query operation with minimal blast radius—worst case, an agent gains visibility into system events without affecting system functionality or data integrity.
From the tool's definition Tool name 'get_instance_logs' and description 'Get instance-level logs' indicate data retrieval with no modification or side effects. The verb 'get' is a standard read operation.
Documented attack patterns abuse exactly the kind of access get_instance_logs 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 get_instance_logs:
{
"version": "1",
"default": "deny",
"tools": {
"get_instance_logs": {}
}
}get_instance_logs 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 instance-level logs instead of virtual server logs. 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 get_instance_logs: 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.
get_instance_logs 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 get_instance_logs 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 get_instance_logs. 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.
get_instance_logs 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.