New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice

workspace_put

Append one chunk of a file into the server-side File Workspace. Use this to push files too big to emit in one response: call it repeatedly with small chunks of the same file (and other files), then call workspace_push once. Omit workspace_id on the very first chunk to get a fresh id back, then re...

SERVERUnClick SOURCE@unclick/mcp-server
Medium RISK CLASS
Category Write
Parameters 42 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/workspace-put.md

What workspace_put does on UnClick

AI agents use workspace_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.

ParameterTypeRequiredDescription
seq number Optional explicit chunk order. Defaults to append order.
path string Yes Repo-relative file path this chunk belongs to.
content string Yes One chunk of the file's UTF-8 content.
workspace_id string Omit on the first chunk to receive a fresh id; reuse it for all chunks and files in one push.

Parameters from the server's own tool schema.

Why workspace_put is rated Medium

workspace_put creates or modifies data on a server-side workspace by appending file chunks. This is a write operation that creates data structures (file chunks) in the workspace. It is reversible (chunks can be overwritten or the workspace cleared before calling workspace_push to finalize).

From the tool's definition Append one chunk of a file into the server-side File Workspace. Use this to push files... call it repeatedly with small chunks of the same file

Risk signalsAccepts file system path (path) · Accepts raw HTML/template content (content) · Bulk/mass operation — affects multiple targets

Questions about workspace_put

What does the workspace_put tool do? +

Append one chunk of a file into the server-side File Workspace. Use this to push files too big to emit in one response: call it repeatedly with small chunks of the same file (and other files), then call workspace_push once. Omit workspace_id on the very first chunk to get a fresh id back, then reuse that id for every chunk and every file in the push. 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 workspace_put accept? +

workspace_put accepts 4 parameters: seq, path, content, workspace_id. Required: path, content. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on workspace_put? +

Register the UnClick MCP server in PolicyLayer and add a rule for workspace_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 workspace_put? +

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

Can I rate-limit workspace_put? +

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

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

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

More on UnClick, and thousands of servers like it.

Across the catalogue

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of UnClick's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.