save_container_state

THE RISK

Medium Risk

Why save_container_state needs a policy

Saving container state is a reversible operation that persists data. It modifies the system by storing a snapshot but does not destroy anything or execute arbitrary commands.

From the tool's definition Tool description states it 'Saves the container state to a persistent container' — this is a create/modify operation that writes state persistently but does not delete or irreversibly alter existing data.

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

POLICY

How to control save_container_state

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 save_container_state:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "save_container_state": {
      "limits": [
        {
          "counter": "save_container_state_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

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

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

LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Sandbox MCP Server tools

Destructive exit_container closes a container to cleanup environment when finished Execute execute_command_in_container Runs commands in a container Execute create_container_environment Creates a new Docker container with specified image Write create_file_in_container Creates a file in a container Write export_dockerfile exports a docker file to create a persistant environment

All 6 Sandbox MCP Server tools →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about save_container_state

What does the save_container_state tool do? +

Saves the container state to a persistent 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 save_container_state? +

Register the Sandbox MCP Server MCP server in PolicyLayer and add a rule for save_container_state: 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 save_container_state? +

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

Can I rate-limit save_container_state? +

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

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

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

CHECK YOUR STACK →