contract-testing_add_label_to_pacticipant

Apply a label to a pacticipant. Parameters: - pacticipantName (string) *required*: Name of the pacticipant - labelName (string) *required*: Name of the label

SERVERSmartBear MCP SOURCESmartBear/smartbear-mcp

Medium RISK CLASS

Category Write

Parameters 22 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-add-label-to-pacticipant.md

WHAT IT DOES

What contract-testing_add_label_to_pacticipant does on SmartBear MCP

AI agents use contract-testing_add_label_to_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
`labelName`	string	Yes	Name of the label
`pacticipantName`	string	Yes	Name of the pacticipant

Parameters from the server's own tool schema.

RISK

Why contract-testing_add_label_to_pacticipant is rated Medium

This tool modifies state by adding labels to pacticipants in PactFlow (a contract testing platform). Labels are metadata that can be used for organization and filtering. The operation is reversible (labels can typically be removed), making it Write rather than Destructive.

From the tool's definition The tool 'contract-testing_add_label_to_pacticipant' applies a label to a pacticipant, which is a create/modify operation that changes metadata associated with a participant in a contract testing system.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

contract-testing_add_label_to_pacticipant Rate-limited

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

FAQ

Questions about contract-testing_add_label_to_pacticipant

What does the contract-testing_add_label_to_pacticipant tool do? +

Apply a label to a pacticipant. Parameters: - pacticipantName (string) *required*: Name of the pacticipant - labelName (string) *required*: Name of the label. 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_add_label_to_pacticipant accept? +

contract-testing_add_label_to_pacticipant accepts 2 parameters: labelName, pacticipantName. Required: labelName, 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_add_label_to_pacticipant? +

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

contract-testing_add_label_to_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_add_label_to_pacticipant? +

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

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

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

add-tag on Kanban MCP Server →kb_add on Persistent Kb →create-label on Meme MCP Server →add_video on Mcptube Vision → The MCP Attack Database →

Guides

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