create_dev_environment · MCP Developer Server MCP

WHAT IT DOES

What create_dev_environment does on MCP Developer Server

AI agents invoke create_dev_environment to trigger actions in MCP Developer Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why create_dev_environment needs a policy

Creating a development environment involves provisioning Docker containers, installing software, and configuring services. This goes beyond a simple write operation as it triggers external execution of container orchestration, installation scripts, and environment setup. The blast radius is high because misconfiguration could expose services, consume significant resources, or create insecure environments.

From the tool's definition 'Create a development environment with pre-configured tools' — spins up a new containerized dev environment, which involves executing Docker container creation and configuration operations

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_dev_environment Rate-limited

create_dev_environment stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "create_dev_environment": {
      "limits": [
        {
          "counter": "create_dev_environment_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches MCP Developer Server, so you can run agents against it safely.

FAQ

Questions about create_dev_environment

What does the create_dev_environment tool do? +

Create a development environment with pre-configured tools. It is categorised as a Execute tool in the MCP Developer Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on create_dev_environment? +

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

What risk level is create_dev_environment? +

create_dev_environment is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit create_dev_environment? +

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

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

create_dev_environment is provided by the MCP Developer Server MCP server (ra86-dev/mcpdev-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.