tailscale_update_user_role

// WHEN AI AGENTS USE THIS TOOL

AI agents use tailscale_update_user_role to create or modify resources in Tailscale. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

// WHY ENFORCE A POLICY ON TAILSCALE_UPDATE_USER_ROLE

Without a policy, an AI agent could call tailscale_update_user_role repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach Tailscale.

// RECOMMENDED POLICY

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

tailscale.yaml

tools:
  tailscale_update_user_role:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full Tailscale policy for all 89 tools.

// DETAILS

Tool Name tailscale_update_user_role

Category Write

MCP Server Tailscale MCP Server

Risk Level Medium

// MORE TAILSCALE TOOLS

Destructive tailscale_delete_device Destructive tailscale_delete_device_invite Destructive tailscale_delete_device_posture_attribute Destructive tailscale_delete_key Destructive tailscale_delete_log_stream_config Destructive tailscale_delete_posture_integration Destructive tailscale_delete_service Destructive tailscale_delete_user

View all 89 tools →

// WHAT CAN GO WRONG

Agents calling write-class tools like tailscale_update_user_role have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

// OTHER WRITE TOOLS ACROSS MCP SERVERS

Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

Firecrawl Web Scraping Server firecrawl_generate_llmstxt AbraFlexi contact_create AbraFlexi contact_update AbraFlexi evidence_create AbraFlexi evidence_update AbraFlexi invoice_issued_update

// RELATED READING

// FAQ

What does the tailscale_update_user_role tool do? +

Update a user's role in the tailnet.. It is categorised as a Write tool in the Tailscale MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on tailscale_update_user_role? +

Add a rule in your Intercept YAML policy under the tools section for tailscale_update_user_role. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the Tailscale MCP server.

What risk level is tailscale_update_user_role? +

tailscale_update_user_role is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit tailscale_update_user_role? +

Yes. Add a rate_limit block to the tailscale_update_user_role rule in your Intercept 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 tailscale_update_user_role completely? +

Set action: deny in the Intercept policy for tailscale_update_user_role. 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 tailscale_update_user_role? +

tailscale_update_user_role is provided by the Tailscale MCP server (@yawlabs/tailscale-mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Let agents act without letting them run wild.