contract-testing_publish_consumer_contracts

SERVERSmartBear MCP SOURCESmartBear/smartbear-mcp

Medium RISK CLASS

Category Write

Parameters 63 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-publish-consumer-contracts.md

WHAT IT DOES

What contract-testing_publish_consumer_contracts does on SmartBear MCP

AI agents use contract-testing_publish_consumer_contracts 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
`tags`	array	—	Version tags (e.g. 'main', 'staging')
`branch`	string	—	Branch name of the consumer
`buildUrl`	string	—	URL of the CI build that produced these contracts
`contracts`	array	Yes	Contracts to publish
`pacticipantName`	string	Yes	Name of the consumer application
`pacticipantVersionNumber`	string	Yes	Version number of the consumer

Parameters from the server's own tool schema.

RISK

Why contract-testing_publish_consumer_contracts is rated Medium

Publishing contracts to a broker modifies state in PactFlow/Pact Broker by creating or updating contract records. This is reversible (contracts can be unpublished or overwritten) and has no financial impact or code execution.

From the tool's definition Tool name includes 'publish' and description states 'Publish one or more consumer Pact contracts to the Pact Broker or PactFlow' — this creates/uploads contract metadata to an external service.

Risk signalsAccepts raw HTML/template content (contracts[].content) · High parameter count (11 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

contract-testing_publish_consumer_contracts Rate-limited

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

FAQ

Questions about contract-testing_publish_consumer_contracts

What does the contract-testing_publish_consumer_contracts tool do? +

Publish one or more consumer Pact contracts to the Pact Broker or PactFlow, with branch and tag metadata. Parameters: - pacticipantName (string) *required*: Name of the consumer application - pacticipantVersionNumber (string) *required*: Version number of the consumer - contracts (array) *required*: Contracts to publish - tags (array): Version tags (e.g. 'main', 'staging') - branch (string): Branch name of the consumer - buildUrl (string): URL of the CI build that produced these contracts. 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_publish_consumer_contracts accept? +

contract-testing_publish_consumer_contracts accepts 6 parameters: tags, branch, buildUrl, contracts, pacticipantName, pacticipantVersionNumber. Required: contracts, pacticipantName, pacticipantVersionNumber. The full parameter table on this page comes from the server's own tool schema.

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

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

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

Can I rate-limit contract-testing_publish_consumer_contracts? +

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

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

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