Devbox

38 tools. 31 can modify or destroy data without limits.

2 destructive tools with no built-in limits. Policy required.

Last updated:

31 can modify or destroy data
7 read-only
38 tools total
Read (7) Write / Execute (29) Destructive / Financial (2)

Destructive tools (devbox_projects, devbox_runs_cancel_all) permanently delete resources. There is no undo. An agent calling these in a retry loop causes irreversible damage.

Write operations (devbox_context_annotate, devbox_context_register, devbox_context_resolve_contradiction) modify state. Without rate limits, an agent can make hundreds of changes in seconds — faster than any human can review or revert.

Execute tools (devbox_admin, devbox_agent_handoff, devbox_billing) trigger processes with side effects. Builds, notifications, workflows — all fired without throttling.

One command. Full control.

Intercept sits between your agent and Devbox. Every tool call checked against your policy before it executes — so your agent can do its job without breaking things.

npx -y @policylayer/intercept scan -- npx -y @devbox-mcp-server
Scans every tool. Generates a policy. Starts enforcing.
Works with Claude Code · Cursor · Claude Desktop · Windsurf · any MCP client
Deny destructive operations
devbox_projects:
  rules:
    - action: deny

Destructive tools should never be available to autonomous agents without human approval.

Rate limit write operations
devbox_context_annotate:
  rules:
    - rate_limit: 30/hour

Prevents bulk unintended modifications from agents caught in loops.

Cap read operations
devbox_approvals:
  rules:
    - rate_limit: 60/minute

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Can an AI agent delete data through the Devbox MCP server? +

Yes. The Devbox server exposes 2 destructive tools including devbox_projects, devbox_runs_cancel_all. These permanently remove resources with no undo. Intercept blocks destructive tools by default so they never reach the upstream server.

How do I prevent bulk modifications through Devbox? +

The Devbox server has 6 write tools including devbox_context_annotate, devbox_context_register, devbox_context_resolve_contradiction. Set rate limits in your policy file -- for example, rate_limit: 10/hour prevents an agent from making more than 10 modifications per hour. Intercept enforces this at the transport layer.

How many tools does the Devbox MCP server expose? +

38 tools across 4 categories: Destructive, Execute, Read, Write. 7 are read-only. 31 can modify, create, or delete data.

How do I add Intercept to my Devbox setup? +

One line change. Instead of running the Devbox server directly, prefix it with Intercept: intercept -c devbox.yaml -- npx -y @devbox-mcp-server. Download a pre-built policy from policylayer.com/policies/devbox and adjust the limits to match your use case.

Other MCP servers with similar tools.

Starter policies available for each. Same risk classification, same one-command setup.

policylayer/intercept

Control every MCP tool call
your agent makes.

Set budgets, approvals, and hard limits across MCP servers.

npx -y @policylayer/intercept init
Protect your agent in 30 seconds. Scans your MCP config and generates enforcement policies for every server.
// GET IN TOUCH

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

Message sent.

We'll get back to you soon.