file_sync_list
List the files stored for a project with their content hash, size, and version. This is the diff surface: compare your local file hashes against content_hash.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/file-sync-list.md
What file_sync_list does on UnClick
AI agents call file_sync_list to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
project | string | Yes | Project to list. |
Parameters from the server's own tool schema.
Why file_sync_list is rated Low
This tool retrieves file metadata and hashes for comparison purposes. It performs no write, deletion, or execution operations. The blast radius of misuse is minimal—an attacker gains visibility into project file structure and versions, but cannot modify, delete, or execute code. This is a standard Read operation.
From the tool's definition Tool name and description indicate listing and querying: 'List the files stored for a project' with metadata retrieval (content_hash, size, version). The description explicitly frames it as a comparison surface for local vs.
Attacks that exploit this kind of access
The rule that runs file_sync_list safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For file_sync_list, this is the rule to start with:
file_sync_list is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every file_sync_list call is checked against it from then on.
Questions about file_sync_list
List the files stored for a project with their content hash, size, and version. This is the diff surface: compare your local file hashes against content_hash. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
file_sync_list accepts 1 parameter: project. Required: project. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for file_sync_list: 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 UnClick. Nothing to install.
file_sync_list 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 file_sync_list 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 file_sync_list. 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.
file_sync_list is provided by the UnClick MCP server (@unclick/mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue