browse_folder
AI agents call browse_folder to retrieve information from Syncthing MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
The tool name 'browse_folder' most naturally implies retrieving or listing folder contents without modification. The server context (file sync monitoring) and sibling tools (all get_* operations are read-only) support this classification. While the empty description reduces confidence, the semantic meaning of 'browse' strongly indicates data retrieval rather than modification, execution, or destructive actions.
From the tool's definition Tool name 'browse_folder' suggests directory/file listing functionality. The server description indicates it manages 'file synchronization instances' and related tools like 'get_config', 'get_completion', 'get_errors' perform read-only queries.
Attacks that exploit this kind of access
browse_folder. It is categorised as a Read tool in the Syncthing MCP Server MCP Server, which means it retrieves data without modifying state.
Register the Syncthing MCP Server MCP server in PolicyLayer and add a rule for browse_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.
browse_folder is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the browse_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 browse_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.
browse_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 →