file_sync_put

Write one file's bytes into your account's private file-sync store (a Storage bucket, scoped to your account). content is base64; the server computes the content hash and size. Overwrites on repeat.

SERVERUnClick SOURCE@unclick/mcp-server

Medium RISK CLASS

Category Write

Parameters 33 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/file-sync-put.md

WHAT IT DOES

What file_sync_put does on UnClick

AI agents use file_sync_put to create or update resources in UnClick, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your UnClick environment.

Parameter	Type	Required	Description
`path`	string	Yes	Repo-relative file path within the project.
`content`	string	Yes	The file's bytes, base64-encoded.
`project`	string	Yes	Project grouping (a single name segment).

Parameters from the server's own tool schema.

RISK

Why file_sync_put is rated Medium

This tool creates or modifies files in a user's private storage account. While the action is reversible (files can be deleted or overwritten later), it does irreversibly change the current state of stored data. The scope is limited to the user's own account (not shared/global), reducing blast radius compared to cross-account writes.

From the tool's definition Tool description explicitly states 'Write one file's bytes into your account's private file-sync store' and 'Overwrites on repeat.' The verb 'Write' and the mechanism of storing file content in a user-scoped bucket are direct indicators of data modification.

Risk signalsAccepts file system path (path) · Accepts raw HTML/template content (content)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs file_sync_put 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_put, this is the rule to start with:

file_sync_put Rate-limited

file_sync_put 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": {
    "file_sync_put": {
      "limits": [
        {
          "counter": "file_sync_put_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every file_sync_put call is checked against it from then on.

FAQ

Questions about file_sync_put

What does the file_sync_put tool do? +

Write one file's bytes into your account's private file-sync store (a Storage bucket, scoped to your account). content is base64; the server computes the content hash and size. Overwrites on repeat. It is categorised as a Write tool in the UnClick MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does file_sync_put accept? +

file_sync_put accepts 3 parameters: path, content, project. Required: path, content, project. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on file_sync_put? +

Register the UnClick MCP server in PolicyLayer and add a rule for file_sync_put: 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.

What risk level is file_sync_put? +

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

Can I rate-limit file_sync_put? +

Yes. Add a rate_limit block to the file_sync_put 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 file_sync_put completely? +

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

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

KEEP EXPLORING

More on UnClick, and thousands of servers like it.

This server

All 1662 UnClick tools →

Across the catalogue

write_file on 0sec → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →