Critical Risk →

deploy_server_snapshot

Deploy/restore a server configuration from a snapshot

How to control deploy_server_snapshot ↓

What deploy_server_snapshot does on TeamSpeak MCP

AI agents call deploy_server_snapshot to permanently remove resources in TeamSpeak MCP — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Critical Risk

Why deploy_server_snapshot needs a policy

Deploying or restoring a server snapshot overwrites the entire current server configuration with the snapshot state. This is an irreversible destructive action that replaces all existing settings, channels, permissions, and groups — potentially destroying any configuration changes made since the snapshot was taken. The blast radius is critical as it affects the entire TeamSpeak server.

From the tool's definition Deploy/restore a server configuration from a snapshot

Documented attack patterns abuse exactly the kind of access deploy_server_snapshot gives an agent:

How to control deploy_server_snapshot

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 deploy_server_snapshot:

policy.json
{
  "version": "1",
  "default": "deny",
  "hide": [
    "deploy_server_snapshot"
  ]
}

deploy_server_snapshot disappears from the agent's tool list entirely, and any attempt to call it is denied. The rest of the server keeps working.

  1. Create a free account and register TeamSpeak MCP — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
RESTRICT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about deploy_server_snapshot

What does the deploy_server_snapshot tool do? +

Deploy/restore a server configuration from a snapshot. It is categorised as a Destructive tool in the TeamSpeak MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on deploy_server_snapshot? +

Register the TeamSpeak MCP server in PolicyLayer and add a rule for deploy_server_snapshot: 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.

What risk level is deploy_server_snapshot? +

deploy_server_snapshot is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit deploy_server_snapshot? +

Yes. Add a rate_limit block to the deploy_server_snapshot 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.

How do I block deploy_server_snapshot completely? +

Set action: deny in the PolicyLayer policy for deploy_server_snapshot. 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.

What MCP server provides deploy_server_snapshot? +

deploy_server_snapshot 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.

Enforce policy on every TeamSpeak MCP tool call.

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.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.