contract-testing_get_bdct_consumer_contract_by_consumer_version

SERVERSmartBear MCP SOURCESmartBear/smartbear-mcp

Low RISK CLASS

Category Read

Parameters 44 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-bdct-consumer-contract-by-consumer-version.md

WHAT IT DOES

What contract-testing_get_bdct_consumer_contract_by_consumer_version does on SmartBear MCP

AI agents call contract-testing_get_bdct_consumer_contract_by_consumer_version 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
`consumerName`	string	Yes	Name of the consumer
`providerName`	string	Yes	Name of the provider
`consumerVersionNumber`	string	Yes	Consumer version number
`providerVersionNumber`	string	Yes	Provider version number

Parameters from the server's own tool schema.

RISK

Why contract-testing_get_bdct_consumer_contract_by_consumer_version is rated Low

The tool retrieves contract testing data (Pact contracts) based on consumer-provider version identifiers. It has no side effects, does not modify data, and does not execute code or trigger external operations. This is a straightforward read operation with minimal blast radius if misused by an AI agent.

From the tool's definition Tool name includes 'get' and description states 'Fetch the consumer Pact contract' — this is a retrieval operation that queries contract data without modifying, deleting, or executing anything.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

contract-testing_get_bdct_consumer_contract_by_consumer_version Allowed

contract-testing_get_bdct_consumer_contract_by_consumer_version 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_bdct_consumer_contract_by_consumer_version": {}
  }
}

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

FAQ

Questions about contract-testing_get_bdct_consumer_contract_by_consumer_version

What does the contract-testing_get_bdct_consumer_contract_by_consumer_version tool do? +

Fetch the consumer Pact contract for a specific consumer-provider version pair in Bi-Directional Contract Testing. Parameters: - providerName (string) *required*: Name of the provider - providerVersionNumber (string) *required*: Provider version number - consumerName (string) *required*: Name of the consumer - consumerVersionNumber (string) *required*: Consumer version number. 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_bdct_consumer_contract_by_consumer_version accept? +

contract-testing_get_bdct_consumer_contract_by_consumer_version accepts 4 parameters: consumerName, providerName, consumerVersionNumber, providerVersionNumber. Required: consumerName, providerName, consumerVersionNumber, providerVersionNumber. 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_bdct_consumer_contract_by_consumer_version? +

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

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

Can I rate-limit contract-testing_get_bdct_consumer_contract_by_consumer_version? +

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

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

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