contract-testing_update_pacticipant_version

SERVERSmartBear MCP SOURCESmartBear/smartbear-mcp

Medium RISK CLASS

Category Write

Parameters 32 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-pacticipant-version.md

WHAT IT DOES

What contract-testing_update_pacticipant_version does on SmartBear MCP

AI agents use contract-testing_update_pacticipant_version 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
`buildUrl`	string	—	URL of the CI build that produced this version
`versionNumber`	string	Yes	Version number to update
`pacticipantName`	string	Yes	Name of the pacticipant

Parameters from the server's own tool schema.

RISK

Why contract-testing_update_pacticipant_version is rated Medium

This tool creates or modifies data (pacticipant version metadata) in a reversible manner. It does not execute arbitrary code, delete data irreversibly, or move money. The 'update' operation is characteristic of Write category.

From the tool's definition Tool name contains 'update' and description states 'Update metadata for a specific pacticipant version.' The parameters allow modification of pacticipant version metadata including buildUrl, which is a reversible change to data.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

contract-testing_update_pacticipant_version Rate-limited

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

FAQ

Questions about contract-testing_update_pacticipant_version

What does the contract-testing_update_pacticipant_version tool do? +

Update metadata for a specific pacticipant version. Parameters: - pacticipantName (string) *required*: Name of the pacticipant - versionNumber (string) *required*: Version number to update - buildUrl (string): URL of the CI build that produced this version. 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_pacticipant_version accept? +

contract-testing_update_pacticipant_version accepts 3 parameters: buildUrl, versionNumber, pacticipantName. Required: 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_update_pacticipant_version? +

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

contract-testing_update_pacticipant_version 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_pacticipant_version? +

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

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

contract-testing_update_pacticipant_version 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 →