accept_device · Syncthing MCP Server MCP: Risk & Policy

WHAT IT DOES

What accept_device does on Syncthing MCP Server

AI agents use accept_device to create or update resources in Syncthing MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Syncthing MCP Server environment.

WHY IT NEEDS A POLICY

Why accept_device needs a policy

This tool modifies system configuration by accepting and adding a new device to Syncthing's configuration. While not destructive (the change is reversible by removing the device), it is clearly a Write operation as it creates/adds a new configuration entry.

From the tool's definition Tool description states it will 'Accept a pending device connection request and add it to the configuration.' The action of accepting a device and adding it to configuration is a permanent modification that creates a new entry in the system's configuration.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

accept_device Rate-limited

accept_device stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "accept_device": {
      "limits": [
        {
          "counter": "accept_device_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches Syncthing MCP Server, so you can run agents against it safely.

FAQ

Questions about accept_device

What does the accept_device tool do? +

Accept a pending device connection request and add it to the configuration. It is categorised as a Write tool in the Syncthing MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on accept_device? +

Register the Syncthing MCP Server MCP server in PolicyLayer and add a rule for accept_device: 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 Syncthing MCP Server. Nothing to install.

What risk level is accept_device? +

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

Can I rate-limit accept_device? +

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

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

accept_device is provided by the Syncthing MCP Server MCP server (zaphodsdad/syncthing-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.