contract-testing_get_branch_versions

Retrieve all versions published from a specific branch of a pacticipant. Parameters: - pacticipantName (string) *required*: Name of the pacticipant - branchName (string) *required*: Name of the branch - pageNumber (number): Page number - pageSize (number): Results per page

SERVERSmartBear MCP SOURCESmartBear/smartbear-mcp
Low RISK CLASS
Category Read
Parameters 42 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-branch-versions.md

What contract-testing_get_branch_versions does on SmartBear MCP

AI agents call contract-testing_get_branch_versions 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.

ParameterTypeRequiredDescription
pageSize number Results per page
branchName string Yes Name of the branch
pageNumber number Page number
pacticipantName string Yes Name of the pacticipant

Parameters from the server's own tool schema.

Why contract-testing_get_branch_versions is rated Low

This tool retrieves versioning information from a contract testing system (PactFlow). It performs a query operation that fetches data without modifying, deleting, or executing any operations. The parameters support simple data retrieval with pagination, confirming it is a Read operation with low severity as misuse would only expose non-sensitive metadata about published versions.

From the tool's definition Tool description explicitly states 'Retrieve all versions' with parameters for pacticipantName, branchName, pageNumber, and pageSize. The verb 'Retrieve' and the read-only parameters (pagination) indicate a query operation with no side effects.

Questions about contract-testing_get_branch_versions

What does the contract-testing_get_branch_versions tool do? +

Retrieve all versions published from a specific branch of a pacticipant. Parameters: - pacticipantName (string) *required*: Name of the pacticipant - branchName (string) *required*: Name of the branch - pageNumber (number): Page number - pageSize (number): Results per page. 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_branch_versions accept? +

contract-testing_get_branch_versions accepts 4 parameters: pageSize, branchName, pageNumber, pacticipantName. Required: branchName, pacticipantName. 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_branch_versions? +

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

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

Can I rate-limit contract-testing_get_branch_versions? +

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

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

contract-testing_get_branch_versions 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.

More on SmartBear, and thousands of servers like it.

// THE MCP REGISTRY

PolicyLayer tracks 44,603 MCP servers and 515,000+ tools.

Every server has a live record: who publishes it, whether it answers without auth, its risk grade, every tool classified, the recommended policy. This page is one line of SmartBear's. Pull the full record:

Teams ship this data inside their own products. See what a licence covers →

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.