contract-testing_record_release

SERVERSmartBear MCP SOURCESmartBear/smartbear-mcp

Medium RISK CLASS

Category Write

Parameters 33 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-record-release.md

WHAT IT DOES

What contract-testing_record_release does on SmartBear MCP

AI agents use contract-testing_record_release 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
`environmentId`	string	Yes	UUID of the target environment
`versionNumber`	string	Yes	Version number that was released
`pacticipantName`	string	Yes	Name of the pacticipant that was released

Parameters from the server's own tool schema.

RISK

Why contract-testing_record_release is rated Medium

This tool records/creates a release entry in PactFlow, associating a version with an environment. It is a Write operation (creating a new record). Severity is high because incorrectly recording a release to the wrong environment could cause downstream contract testing gates to pass or fail incorrectly, potentially allowing incompatible services to be deployed to production.

From the tool's definition Record that a version of a pacticipant has been released to an environment

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs contract-testing_record_release 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_record_release, this is the rule to start with:

contract-testing_record_release Rate-limited

contract-testing_record_release 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_record_release": {
      "limits": [
        {
          "counter": "contract-testing_record_release_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_record_release call is checked against it from then on.

FAQ

Questions about contract-testing_record_release

What does the contract-testing_record_release tool do? +

Record that a version of a pacticipant has been released to an environment (for mobile/library release workflows). Parameters: - pacticipantName (string) *required*: Name of the pacticipant that was released - versionNumber (string) *required*: Version number that was released - environmentId (string) *required*: UUID of the target 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_record_release accept? +

contract-testing_record_release accepts 3 parameters: environmentId, versionNumber, pacticipantName. Required: environmentId, versionNumber, pacticipantName. The full parameter table on this page comes from the server's own tool schema.

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

Register the SmartBear MCP server in PolicyLayer and add a rule for contract-testing_record_release: 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_record_release? +

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

Can I rate-limit contract-testing_record_release? +

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

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

contract-testing_record_release 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_record_checkpoint on Team Manager MCP → The MCP Attack Database →

Guides

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