file_sync_pull
Return short-lived (5 min) signed download URLs for the requested files (or all files in the project). URLs fetch the exact stored bytes.
This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/file-sync-pull.md
What file_sync_pull does on UnClick
AI agents call file_sync_pull 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 |
|---|---|---|---|
paths | array | — | Optional: specific paths. Omit for all. |
project | string | Yes | Project to pull from. |
Parameters from the server's own tool schema.
Why file_sync_pull is rated Low
This tool retrieves data (files) without side effects. It generates signed URLs for downloading content but does not create, modify, delete, or execute anything. The short-lived nature of the URLs (5 min expiration) further limits risk.
From the tool's definition Tool returns download URLs to fetch stored files; described as fetching 'exact stored bytes' with no modification or deletion capability.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs file_sync_pull 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_pull, this is the rule to start with:
file_sync_pull 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_pull call is checked against it from then on.
Questions about file_sync_pull
Return short-lived (5 min) signed download URLs for the requested files (or all files in the project). URLs fetch the exact stored bytes. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
file_sync_pull accepts 2 parameters: paths, 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_pull: 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_pull 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_pull 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_pull. 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_pull 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