create_environment · Zephyr Scale MCP Server MCP

WHAT IT DOES

What create_environment does on Zephyr Scale MCP Server

AI agents use create_environment to create or update resources in Zephyr Scale MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Zephyr Scale MCP Server environment.

WHY IT NEEDS A POLICY

Why create_environment needs a policy

This tool creates a new environment entity, which is a reversible write operation. It does not execute tests, delete data, or move money. The severity is medium because creating test environments could affect test execution workflows and potentially impact many dependent tests, but the action is reversible through deletion or modification.

From the tool's definition Tool name 'create_environment' and description 'Create a new environment' indicate creation of a new resource. In the context of a test management system (Zephyr Scale), this creates a test environment configuration.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_environment Rate-limited

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

View as policy code

policy.json

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

LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about create_environment

What does the create_environment tool do? +

Create a new environment. It is categorised as a Write tool in the Zephyr Scale 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 create_environment? +

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

What risk level is create_environment? +

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

Can I rate-limit create_environment? +

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

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

create_environment is provided by the Zephyr Scale MCP Server MCP server (metquay/zephyr-scale-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.