contract-testing_get_bdct_cross-contract_verification_results

SERVERSmartBear MCP SOURCESmartBear/smartbear-mcp

Low RISK CLASS

Category Read

Parameters 22 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-cross-contract-verification-results.md

WHAT IT DOES

What contract-testing_get_bdct_cross-contract_verification_results does on SmartBear MCP

AI agents call contract-testing_get_bdct_cross-contract_verification_results 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
`providerVersionNumber`	string	Yes	Provider version number

Parameters from the server's own tool schema.

RISK

Why contract-testing_get_bdct_cross-contract_verification_results is rated Low

This tool retrieves existing cross-contract verification test results from a Bi-Directional Contract Testing system. It queries data based on provider name and version without side effects. No data is created, modified, deleted, or executed. The blast radius of misuse is limited to potential information disclosure of test results.

From the tool's definition Tool name contains 'get' and description states 'Fetch the cross-contract verification results' — pure retrieval with no modification, deletion, or execution of code/commands.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

contract-testing_get_bdct_cross-contract_verification_results Allowed

contract-testing_get_bdct_cross-contract_verification_results 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_cross-contract_verification_results": {}
  }
}

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

FAQ

Questions about contract-testing_get_bdct_cross-contract_verification_results

What does the contract-testing_get_bdct_cross-contract_verification_results tool do? +

Fetch the cross-contract verification results for a given provider version in Bi-Directional Contract Testing. Parameters: - providerName (string) *required*: Name of the provider - providerVersionNumber (string) *required*: Provider 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_cross-contract_verification_results accept? +

contract-testing_get_bdct_cross-contract_verification_results accepts 2 parameters: providerName, providerVersionNumber. Required: providerName, 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_cross-contract_verification_results? +

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

contract-testing_get_bdct_cross-contract_verification_results 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_cross-contract_verification_results? +

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

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

contract-testing_get_bdct_cross-contract_verification_results 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_event_results on CTFtime MCP Server →get_cocktail_by_category on Cocktails RAG MCP Server →get_torrent_detail on M-Team MCP Server →aiva_get_affiliate on AIVA MCP Server → The MCP Attack Database →

Guides

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