contract-testing_patch_pacticipant

SERVERSmartBear MCP SOURCESmartBear/smartbear-mcp

Medium RISK CLASS

Category Write

Parameters 61 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-patch-pacticipant.md

WHAT IT DOES

What contract-testing_patch_pacticipant does on SmartBear MCP

AI agents use contract-testing_patch_pacticipant 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
`mainBranch`	string	—	Name of the main/trunk branch (e.g. 'main')
`displayName`	string	—	Human-readable display name
`repositoryUrl`	string	—	URL of the source repository
`repositoryName`	string	—	Repository name
`pacticipantName`	string	Yes	Name of the pacticipant to update
`repositoryNamespace`	string	—	Repository namespace/organisation

Parameters from the server's own tool schema.

RISK

Why contract-testing_patch_pacticipant is rated Medium

This tool modifies pacticipant metadata in a reversible manner (partial updates to fields like displayName, branch name, repository details). It does not delete data (ruling out Destructive), does not execute arbitrary code (ruling out Execute), does not move money (ruling out Financial), and does not merely read data (ruling out Read). The Write category is appropriate for metadata modifications.

From the tool's definition Tool description states 'Partially update a pacticipant's metadata — only fields provided are changed.' The parameters include displayName, mainBranch, repositoryName, repositoryNamespace, and repositoryUrl, which are all metadata fields being modified.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

contract-testing_patch_pacticipant Rate-limited

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

FAQ

Questions about contract-testing_patch_pacticipant

What does the contract-testing_patch_pacticipant tool do? +

Partially update a pacticipant's metadata — only fields provided are changed. Parameters: - pacticipantName (string) *required*: Name of the pacticipant to update - displayName (string): Human-readable display name - mainBranch (string): Name of the main/trunk branch (e.g. 'main') - repositoryName (string): Repository name - repositoryNamespace (string): Repository namespace/organisation - repositoryUrl (string): URL of the source repository. 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_patch_pacticipant accept? +

contract-testing_patch_pacticipant accepts 6 parameters: mainBranch, displayName, repositoryUrl, repositoryName, pacticipantName, repositoryNamespace. Required: 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_patch_pacticipant? +

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

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

Can I rate-limit contract-testing_patch_pacticipant? +

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

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

contract-testing_patch_pacticipant 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

The MCP Attack Database →

Guides

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