accept_folder
AI agents use accept_folder 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.
Based on the tool name and server context, 'accept_folder' likely accepts/approves a folder shared by a remote device in Syncthing, adding it to the local configuration. This is a Write operation as it modifies the sync configuration by adding a new folder. The description is empty, lowering confidence.
From the tool's definition Tool name 'accept_folder' on a Syncthing MCP server that manages folder configurations and device connections.
Attacks that exploit this kind of access
accept_folder. 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.
Register the Syncthing MCP Server MCP server in PolicyLayer and add a rule for accept_folder: 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.
accept_folder is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the accept_folder 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 accept_folder. 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.
accept_folder 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 →