AI agents use add_log_entry 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 (writes) a log entry, which is a reversible operation—log entries can be deleted or cleared. It does not execute code, delete data irreversibly, move money, or read sensitive information. The blast radius is minimal: a malicious agent could clutter logs or add misleading entries, but this is easily remediated and does not compromise the server's integrity, permissions, or core data.
From the tool's definition Tool name 'add_log_entry' and description 'Add a custom entry to the server log' indicate creation of a new log record, which is a reversible write operation.
Documented attack patterns abuse exactly the kind of access add_log_entry 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 add_log_entry:
{
"version": "1",
"default": "deny",
"tools": {
"add_log_entry": {
"limits": [
{
"counter": "add_log_entry_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}add_log_entry 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 a custom entry to the server log. 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 add_log_entry: 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.
add_log_entry 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 add_log_entry 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 add_log_entry. 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.
add_log_entry 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.