exports a docker file to create a persistant environment
AI agents use export_dockerfile 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.
The tool exports/saves a Dockerfile, which is a data creation/modification action (Write category). While it operates in a sandbox context with sibling tools like execute_command_in_container, the export_dockerfile tool itself only produces a file artifact—it does not execute code, delete data, or move money.
From the tool's definition The tool 'exports a docker file to create a persistent environment' – exports and writes Dockerfile content to storage. This is a reversible write operation that creates or modifies a configuration file without destructive effects or code execution.
Documented attack patterns abuse exactly the kind of access export_dockerfile gives an agent:
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 export_dockerfile:
{
"version": "1",
"default": "deny",
"tools": {
"export_dockerfile": {
"limits": [
{
"counter": "export_dockerfile_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}export_dockerfile 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.
Free to start. No card required.
exports a docker file to create a persistant environment. 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.
Register the Sandbox MCP Server MCP server in PolicyLayer and add a rule for export_dockerfile: 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.
export_dockerfile 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 export_dockerfile 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 export_dockerfile. 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.
export_dockerfile 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.
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.