contract-testing_get_pacts_for_verification

SERVERSmartBear MCP SOURCESmartBear/smartbear-mcp

Low RISK CLASS

Category Read

Parameters 61 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/smartbear-mcp/contract-testing-get-pacts-for-verification.md

WHAT IT DOES

What contract-testing_get_pacts_for_verification does on SmartBear MCP

AI agents call contract-testing_get_pacts_for_verification to retrieve information from SmartBear MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Parameter	Type	Required	Description
`providerName`	string	Yes	Name of the provider to get pacts for
`providerVersionTags`	array	—	Tags for the provider version being verified
`includePendingStatus`	boolean	—	Include the pending status in the results
`includeWipPactsSince`	string	—	Include WIP pacts published since this date (ISO 8601)
`providerVersionBranch`	string	—	Branch of the provider version being verified
`consumerVersionSelectors`	array	—	Selectors specifying which consumer versions to include

Parameters from the server's own tool schema.

RISK

Why contract-testing_get_pacts_for_verification is rated Low

This tool retrieves contract testing pact data for verification purposes. It accepts filtering parameters but performs no creation, modification, deletion, execution, or financial operations. The operation is purely informational and returns existing data without altering any state.

From the tool's definition Tool description states 'Retrieve the pacts' and parameters are all input filters (providerName, consumerVersionSelectors, includePendingStatus, includeWipPactsSince, providerVersionBranch, providerVersionTags).

Risk signalsHigh parameter count (17 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

contract-testing_get_pacts_for_verification Allowed

contract-testing_get_pacts_for_verification is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "contract-testing_get_pacts_for_verification": {}
  }
}

ALLOW ONLY 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_get_pacts_for_verification call is checked against it from then on.

FAQ

Questions about contract-testing_get_pacts_for_verification

What does the contract-testing_get_pacts_for_verification tool do? +

Retrieve the pacts that a provider should verify, based on consumer version selectors and WIP/pending pact configuration. Parameters: - providerName (string) *required*: Name of the provider to get pacts for - consumerVersionSelectors (array): Selectors specifying which consumer versions to include - includePendingStatus (boolean): Include the pending status in the results - includeWipPactsSince (string): Include WIP pacts published since this date (ISO 8601) - providerVersionBranch (string): Branch of the provider version being verified - providerVersionTags (array): Tags for the provider version being verified. It is categorised as a Read tool in the SmartBear MCP MCP Server, which means it retrieves data without modifying state.

What parameters does contract-testing_get_pacts_for_verification accept? +

contract-testing_get_pacts_for_verification accepts 6 parameters: providerName, providerVersionTags, includePendingStatus, includeWipPactsSince, providerVersionBranch, consumerVersionSelectors. Required: providerName. The full parameter table on this page comes from the server's own tool schema.

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

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

contract-testing_get_pacts_for_verification is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit contract-testing_get_pacts_for_verification? +

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

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

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

get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server →get-chuck-categories on Jokes MCP Server → The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →