Get sync completion percentage for a folder/device pair.
AI agents call get_completion 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.
This tool only retrieves sync completion data—a metric about synchronization progress. It performs no writes, deletes, executions, or financial operations. The blast radius of misuse is minimal, as an agent could only receive information about sync status. Classification as Read is appropriate with high confidence.
From the tool's definition Tool name 'get_completion' and description 'Get sync completion percentage for a folder/device pair' indicate a read-only query operation that retrieves status information without modifying any state.
Attacks that exploit this kind of access
Get sync completion percentage for a folder/device pair. 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 get_completion: 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.
get_completion 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 get_completion 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 get_completion. 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.
get_completion 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 →