Skip to main content
Glama
@yawlabs/tailscale-mcp

@yawlabs/tailscale-mcp

by YawLabs

Update tailnet settings

tailscale_update_tailnet_settings
Idempotent

Update Tailscale tailnet settings to manage device approval, auto-updates, key expiry, HTTPS certificates, network flow logging, regional routing, and posture identity collection.

Instructions

Update tailnet settings (device approval, auto-updates, key expiry, HTTPS certificates, network flow logging, regional routing, posture identity collection).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "tailscale_update_tailnet_settings"
  }
}

Input Schema

NameRequiredDescriptionDefault
httpsEnabledNoWhether HTTPS certificates are enabled (for tailscale serve/funnel)
usersApprovalOnNoWhether user approval is required
aclsExternalLinkNoURL to the external ACL management system (shown in the admin console)
devicesApprovalOnNoWhether device approval is required
regionalRoutingOnNoWhether regional routing is enabled
devicesAutoUpdatesOnNoWhether auto-updates are enabled
networkFlowLoggingOnNoWhether network flow logging is enabled
devicesKeyDurationDaysNoKey expiry duration in days (whole days, 1-180)
aclsExternallyManagedOnNoWhether ACLs are externally managed (e.g. via GitOps)
postureIdentityCollectionOnNoWhether posture identity collection is enabled
usersRoleAllowedToJoinExternalTailnetsNoWhich user roles can join external tailnets

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv0.23.1
    • changedInput schema / properties / devicesKeyDurationDays / description
      Previous value: -"Key expiry duration in days"New value: +"Key expiry duration in days (whole days, 1-180)"
    • addedInput schema / properties / devicesKeyDurationDays / maximum
      Added value: +180
    • addedInput schema / properties / devicesKeyDurationDays / minimum
      Added value: +1
    • changedInput schema / properties / devicesKeyDurationDays / type
      Previous value: -"number"New value: +"integer"
  2. First observedv0.13.3

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is partly covered. However, the description adds nothing beyond the annotations: it does not say whether omitted fields are preserved or reset, whether admin/owner privileges are required, or whether changes take effect immediately for connected devices. For an 11-field tailnet-wide mutation those are material gaps.

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

Conciseness4/5

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

One front-loaded sentence with a parenthetical list — nothing superfluous and easy to scan. It is slightly redundant since the enumeration duplicates the schema property names, but it is efficiently sized for the tool's scope.

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

Completeness2/5

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

This is an 11-parameter, all-optional mutation on tailnet-wide configuration with no output schema and no statement of update semantics (partial vs. replace), permission requirements, or side effects on enrolled devices. Given the blast radius of settings like device approval and key expiry, the definition leaves too much to inference.

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?

Schema description coverage is 100% with per-property descriptions and a bounded integer range plus one enum, so the schema carries parameter meaning fully. The description merely restates the same field list in prose, adding no units, constraints, defaults, or interaction notes (e.g. key expiry vs. device key rotation). Baseline 3 applies.

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 names a specific verb and resource ("Update tailnet settings") and enumerates the exact settings governed (device approval, auto-updates, key expiry, HTTPS certificates, flow logging, regional routing, posture identity). That makes it distinct from the many device/DNS/ACL siblings. It stops short of explicitly naming tailscale_get_tailnet_settings as its read counterpart or tailscale_update_acl as a separate surface for ACL content.

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

Usage Guidelines2/5

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

There is no when-to-use guidance: no statement about calling get_tailnet_settings first, no note that only supplied fields change, and no routing to alternatives such as update_acl or set_dns_preferences. The agent must infer from the name alone that this is the tailnet-wide settings mutator rather than a device- or DNS-level one.

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