Medium Risk

create_file_in_container

Creates a file in a container

How to control create_file_in_container ↓

What create_file_in_container does on Sandbox MCP Server

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

Medium Risk

Why create_file_in_container needs a policy

This tool creates files within a sandbox container, which is a write operation that modifies the container's filesystem. While reversible through standard deletion, the isolated sandbox environment limits the blast radius compared to direct host filesystem writes.

From the tool's definition Tool name 'create_file_in_container' and description 'Creates a file in a container' explicitly indicate the tool creates (writes) data within an isolated Docker environment.

Documented attack patterns abuse exactly the kind of access create_file_in_container gives an agent:

How to control create_file_in_container

PolicyLayer is an MCP gateway — it sits between your AI agents and Sandbox MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for create_file_in_container:

policy.json
{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_file_in_container": {
      "limits": [
        {
          "counter": "create_file_in_container_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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

  1. Create a free account and register Sandbox MCP Server — nothing to install.
  2. Add this policy — paste it, or build it visually.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
LIMIT THIS TOOL →

Free to start. No card required.

Related tools and policies

Go deeper

Questions about create_file_in_container

What does the create_file_in_container tool do? +

Creates a file in a container. It is categorised as a Write tool in the Sandbox MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on create_file_in_container? +

Register the Sandbox MCP Server MCP server in PolicyLayer and add a rule for create_file_in_container: 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 Sandbox MCP Server. Nothing to install.

What risk level is create_file_in_container? +

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

Can I rate-limit create_file_in_container? +

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

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

create_file_in_container is provided by the Sandbox MCP Server MCP server (tsuchijo/sandbox-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Sandbox MCP Server tool call.

Start from Sandbox MCP Server, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

Free to start. No card required.

6 Sandbox MCP Server tools catalogued and risk-classified — across an index of 43,000+ MCP servers.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.