sandbox_file_ops

Read, write, list, or delete files in a sandbox session.

Server MCP Multi-Language Sandbox pit-cl/mcp-multilang-sandbox
Category Destructive
Risk class Critical
Parameters 00 required

What sandbox_file_ops does on MCP Multi-Language Sandbox

AI agents call sandbox_file_ops to permanently remove resources in MCP Multi-Language Sandbox — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

Why sandbox_file_ops needs a policy

While this tool includes read (Read category) and write (Write category) capabilities, the destructive capability—deleting files—takes precedence under the severity hierarchy. File deletion is irreversible and represents the most severe operation the tool can perform. In a sandbox context with persistent sessions, deleted files cannot be recovered.

From the tool's definition Tool description explicitly states it can 'delete files in a sandbox session.' The ability to irreversibly remove files qualifies as destructive, even though the tool also supports read and write operations.

Questions about sandbox_file_ops

What does the sandbox_file_ops tool do? +

Read, write, list, or delete files in a sandbox session. It is categorised as a Destructive tool in the MCP Multi-Language Sandbox MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

How do I enforce a policy on sandbox_file_ops? +

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

What risk level is sandbox_file_ops? +

sandbox_file_ops is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit sandbox_file_ops? +

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

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

sandbox_file_ops is provided by the MCP Multi-Language Sandbox MCP server (pit-cl/mcp-multilang-sandbox). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

// LOOK UP ANOTHER SERVER

Every MCP server has a record like this.

Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.

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.