sandbox_files_write
Run sandbox-files.write through the Appaloft application operation catalog. Shared with CLI and HTTP/API.
This record as markdown: /tools/appaloft-mcp/sandbox-files-write.md
What sandbox_files_write does on Appaloft
AI agents use sandbox_files_write to create or update resources in Appaloft, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Appaloft environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
path | string | Yes | |
sandboxId | string | Yes | |
contentBase64 | string | Yes |
Parameters from the server's own tool schema.
Why sandbox_files_write is rated Medium
The tool creates or modifies data (files) in a sandbox context. The 'sandbox' qualifier suggests the operation is confined to a sandboxed environment, limiting blast radius to that scope rather than system-wide files. This is reversible (files can be overwritten or deleted by other means), so it is Write rather than Destructive.
From the tool's definition Tool name is 'sandbox_files_write' and description states 'write' operation. The tool is explicitly described as writing files in a sandbox environment.
Risk signalsAccepts file system path (path)
Attacks that exploit this kind of access
The rule that runs sandbox_files_write safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Appaloft, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For sandbox_files_write, this is the rule to start with:
sandbox_files_write 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Appaloft, apply this rule, and every sandbox_files_write call is checked against it from then on.
Questions about sandbox_files_write
Run sandbox-files.write through the Appaloft application operation catalog. Shared with CLI and HTTP/API. It is categorised as a Write tool in the Appaloft MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
sandbox_files_write accepts 3 parameters: path, sandboxId, contentBase64. Required: path, sandboxId, contentBase64. The full parameter table on this page comes from the server's own tool schema.
Register the Appaloft MCP server in PolicyLayer and add a rule for sandbox_files_write: 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 Appaloft. Nothing to install.
sandbox_files_write is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the sandbox_files_write 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 sandbox_files_write. 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.
sandbox_files_write is provided by the Appaloft MCP server (@appaloft/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Appaloft, and thousands of servers like it.
This server
Across the catalogue