Medium Risk

tailscale_set_devices_authorized

Authorize or deauthorize multiple devices in one call. Each device's POST runs in parallel; per-device errors are returned alongside the successes so a partial failure doesn't lose the work that succeeded. Common use: authorize a batch of newly-enrolled CI hosts, or deauthorize a group of devices...

Part of the Tailscale MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents use tailscale_set_devices_authorized 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.

Without a policy, an AI agent could call tailscale_set_devices_authorized 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.

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

tailscale.yaml
tools:
  tailscale_set_devices_authorized:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full Tailscale policy for all 89 tools.

Tool Name tailscale_set_devices_authorized
Category Write
Risk Level Medium

View all 89 tools →

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

Browse the full MCP Attack Database →

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

What does the tailscale_set_devices_authorized tool do? +

Authorize or deauthorize multiple devices in one call. Each device's POST runs in parallel; per-device errors are returned alongside the successes so a partial failure doesn't lose the work that succeeded. Common use: authorize a batch of newly-enrolled CI hosts, or deauthorize a group of devices flagged by a security review.. 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_set_devices_authorized? +

Add a rule in your Intercept YAML policy under the tools section for tailscale_set_devices_authorized. 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_set_devices_authorized? +

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

Can I rate-limit tailscale_set_devices_authorized? +

Yes. Add a rate_limit block to the tailscale_set_devices_authorized 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_set_devices_authorized completely? +

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

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

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.