reject_folder · Syncthing MCP Server MCP: Risk & Policy

WHAT IT DOES

What reject_folder does on Syncthing MCP Server

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

WHY IT NEEDS A POLICY

Why reject_folder needs a policy

This tool modifies data state (rejecting a pending folder share) but does not irreversibly destroy data or execute arbitrary code. The action is reversible—a folder share can be re-offered or accepted later. While it affects folder synchronization configuration, the modification is non-destructive and user-controlled.

From the tool's definition The tool 'reject_folder' performs a dismissal action on a pending folder share offer, which modifies the state of folder sharing relationships by changing a pending offer to a rejected state. This is a reversible modification operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

reject_folder Rate-limited

reject_folder 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": {
    "reject_folder": {
      "limits": [
        {
          "counter": "reject_folder_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 reject_folder

What does the reject_folder tool do? +

Reject and dismiss a pending folder share offer. 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 reject_folder? +

Register the Syncthing MCP Server MCP server in PolicyLayer and add a rule for reject_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.

What risk level is reject_folder? +

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

Can I rate-limit reject_folder? +

Yes. Add a rate_limit block to the reject_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.

How do I block reject_folder completely? +

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

What MCP server provides reject_folder? +

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