Resume all syncing on the instance.
AI agents invoke resume_all to trigger actions in Syncthing MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.
This tool triggers an external operation (resuming synchronization) across all folders/devices on a Syncthing instance. It doesn't merely read data, nor does it create/modify data directly, nor is it irreversible destruction. It initiates a system-wide operational state change that causes Syncthing to begin actively syncing files, which could have broad side effects depending on pending changes.
From the tool's definition Resume all syncing on the instance
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
Resume all syncing on the instance. It is categorised as a Execute tool in the Syncthing MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
Register the Syncthing MCP Server MCP server in PolicyLayer and add a rule for resume_all: 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.
resume_all is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the resume_all 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.
Set action: deny in the PolicyLayer policy for resume_all. 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.
resume_all 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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →