contract-testing_update_environment

SERVERSmartBear MCP SOURCESmartBear/smartbear-mcp

Medium RISK CLASS

Category Write

Parameters 53 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/smartbear-mcp/contract-testing-update-environment.md

WHAT IT DOES

What contract-testing_update_environment does on SmartBear MCP

AI agents use contract-testing_update_environment to create or update resources in SmartBear MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your SmartBear MCP environment.

Parameter	Type	Required	Description
`name`	string	Yes	Unique name for the environment
`teamUuids`	array	—	UUIDs of teams that own this environment
`production`	boolean	Yes	Whether this is a production environment
`displayName`	string	—	Human-readable display name
`environmentId`	string	Yes	UUID of the environment to update

Parameters from the server's own tool schema.

RISK

Why contract-testing_update_environment is rated Medium

This tool creates or modifies data (environment metadata) in a reversible manner. Changes to environment configuration can be undone by updating again with different values. The severity is medium because misconfiguration could affect testing pipelines and team access controls, but the action is not destructive, financial, or code-executing.

From the tool's definition Tool name includes 'update' and description states 'Update an existing environment's metadata.' Parameters allow modification of environment configuration including name, production flag, and team ownership.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs contract-testing_update_environment safely

PolicyLayer is an MCP gateway: it sits between your AI agents and SmartBear MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For contract-testing_update_environment, this is the rule to start with:

contract-testing_update_environment Rate-limited

contract-testing_update_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": {
    "contract-testing_update_environment": {
      "limits": [
        {
          "counter": "contract-testing_update_environment_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect SmartBear MCP, apply this rule, and every contract-testing_update_environment call is checked against it from then on.

FAQ

Questions about contract-testing_update_environment

What does the contract-testing_update_environment tool do? +

Update an existing environment's metadata. Parameters: - environmentId (string) *required*: UUID of the environment to update - name (string) *required*: Unique name for the environment - production (boolean) *required*: Whether this is a production environment - displayName (string): Human-readable display name - teamUuids (array): UUIDs of teams that own this environment. It is categorised as a Write tool in the SmartBear MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

What parameters does contract-testing_update_environment accept? +

contract-testing_update_environment accepts 5 parameters: name, teamUuids, production, displayName, environmentId. Required: name, production, environmentId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on contract-testing_update_environment? +

Register the SmartBear MCP server in PolicyLayer and add a rule for contract-testing_update_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 SmartBear MCP. Nothing to install.

What risk level is contract-testing_update_environment? +

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

Can I rate-limit contract-testing_update_environment? +

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

Set action: deny in the PolicyLayer policy for contract-testing_update_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 contract-testing_update_environment? +

contract-testing_update_environment is provided by the SmartBear MCP server (SmartBear/smartbear-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on SmartBear, and thousands of servers like it.

This server

All 240 SmartBear tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP →team_manager_update_budget on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →