contract-testing_publish_provider_contract

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-provider-contract.md

WHAT IT DOES

What contract-testing_publish_provider_contract does on SmartBear MCP

AI agents use contract-testing_publish_provider_contract 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
`branch`	string	—	Branch name of the provider
`buildUrl`	string	—	URL of the CI build
`contract`	object	Yes	Provider contract (OpenAPI spec) and verification details
`providerName`	string	Yes	Name of the provider application
`pacticipantVersionNumber`	string	Yes	Version number of the provider

Parameters from the server's own tool schema.

RISK

Why contract-testing_publish_provider_contract is rated Medium

Publishing contracts and verification results to PactFlow modifies state in the contract testing platform reversibly—contracts can be updated, replaced, or removed. This is a Write operation (create/modify data), not Execute (no arbitrary code execution), not Destructive (publishing is reversible), and not Financial.

From the tool's definition Tool action is 'Publish...to PactFlow' which creates or modifies contract data in a remote service. Parameters include contract object and metadata (tags, branch, buildUrl) being sent to an external system.

Risk signalsAccepts raw HTML/template content (contract.content) · High parameter count (16 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

contract-testing_publish_provider_contract Rate-limited

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

FAQ

Questions about contract-testing_publish_provider_contract

What does the contract-testing_publish_provider_contract tool do? +

Publish a provider OpenAPI contract and self-verification results to PactFlow (Bi-Directional Contract Testing). Parameters: - providerName (string) *required*: Name of the provider application - pacticipantVersionNumber (string) *required*: Version number of the provider - contract (object) *required*: Provider contract (OpenAPI spec) and verification details - tags (array): Version tags - branch (string): Branch name of the provider - buildUrl (string): URL of the CI build. 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_provider_contract accept? +

contract-testing_publish_provider_contract accepts 6 parameters: tags, branch, buildUrl, contract, providerName, pacticipantVersionNumber. Required: contract, providerName, 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_provider_contract? +

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

contract-testing_publish_provider_contract 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_provider_contract? +

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

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

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