contract-testing_remove_label_from_pacticipant

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

SERVERSmartBear MCP SOURCESmartBear/smartbear-mcp

Critical RISK CLASS

Category Destructive

Parameters 22 required

Recommended Hiddensee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/smartbear-mcp/contract-testing-remove-label-from-pacticipant.md

WHAT IT DOES

What contract-testing_remove_label_from_pacticipant does on SmartBear MCP

AI agents call contract-testing_remove_label_from_pacticipant to permanently remove resources in SmartBear MCP, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.

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_remove_label_from_pacticipant is rated Critical

Removing a label is a destructive operation that deletes a metadata association from a pacticipant in PactFlow. While labels can potentially be re-added, the removal itself is an irreversible action (the label is deleted, not modified). The blast radius is medium as it affects contract testing metadata/categorization but does not destroy contracts or pact data itself.

From the tool's definition "Remove a label from a pacticipant" — the word 'remove' indicates an irreversible deletion of the label association from the pacticipant entity.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

contract-testing_remove_label_from_pacticipant Hidden

contract-testing_remove_label_from_pacticipant is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "hide": [
    "contract-testing_remove_label_from_pacticipant"
  ]
}

RESTRICT 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_remove_label_from_pacticipant call is checked against it from then on.

FAQ

Questions about contract-testing_remove_label_from_pacticipant

What does the contract-testing_remove_label_from_pacticipant tool do? +

Remove a label from a pacticipant. Parameters: - pacticipantName (string) *required*: Name of the pacticipant - labelName (string) *required*: Name of the label. It is categorised as a Destructive tool in the SmartBear MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.

What parameters does contract-testing_remove_label_from_pacticipant accept? +

contract-testing_remove_label_from_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_remove_label_from_pacticipant? +

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

contract-testing_remove_label_from_pacticipant is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.

Can I rate-limit contract-testing_remove_label_from_pacticipant? +

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

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

contract-testing_remove_label_from_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 → Critical-risk tools on this server →

Across the catalogue

remove_video on Mcptube Vision →remove_2fa on cPanel MCP Server →remove_concept on MegaMemory →task_assignees_remove on Vikunja → All critical-risk MCP tools → The MCP Attack Database →

Guides

Govern database agents →Blast radius →Tool call approval →