Skip to main content
Glama
@yawlabs/tailscale-mcp

@yawlabs/tailscale-mcp

by YawLabs

Suspend user

tailscale_suspend_user
DestructiveIdempotent

Suspend a Tailscale user to immediately revoke tailnet access and disconnect their devices; reverse later with the restore user tool.

Instructions

Suspend a user, immediately revoking their access to the tailnet. Their devices will be disconnected. Can be reversed with tailscale_restore_user.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "userId": "<userId>"
    },
    "name": "tailscale_suspend_user"
  }
}

Input Schema

NameRequiredDescriptionDefault
userIdYesThe user ID to suspend

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.23.1
    • addedInput schema / properties / userId / minLength
      Added value: +1
  2. First observedv0.13.3

TDQS

A4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is carried structurally. The description adds concrete blast radius beyond that: access is revoked immediately and the user's devices are disconnected, which is exactly the impact information an agent needs before invoking a destructive tool. It does not mention required permissions or behavior when the user is already suspended.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the action and its immediate effect, then the reversal path. No redundant or ceremonial wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter mutation with no output schema, the description covers effect, reversibility, and safety adequately. The only real gap is error/edge-case behavior (already-suspended users, unknown IDs), which is minor given the idempotent annotation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There is a single parameter with 100% schema description coverage, so the schema already defines userId. The description adds nothing about the ID's origin (e.g. from tailscale_list_users) or format, leaving the baseline of 3 appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource ("Suspend a user") plus the immediate consequence, and explicitly names the inverse operation tailscale_restore_user, which separates it from restore_user. It does not distinguish itself from nearby destructive siblings such as tailscale_delete_user or tailscale_deauthorize_device, so an agent choosing among removal-style operations has to infer the difference.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is clearly implied (temporarily cut off a user's access) and the alternative restore path is named, so the agent knows the reversible option. It stops short of saying when NOT to use it, e.g. when permanent removal via delete_user is desired.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools