contract-testing_list_branches
Retrieve all branches for a given pacticipant, with optional filtering and pagination. Parameters: - pacticipantName (string) *required*: Name of the pacticipant - q (string): Filter branches by name - pageNumber (number): Page number (default: 1) - pageSize (number): Results per page (default: 100)
This record as markdown: /tools/smartbear-mcp/contract-testing-list-branches.md
What contract-testing_list_branches does on SmartBear MCP
AI agents call contract-testing_list_branches 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 |
|---|---|---|---|
q | string | — | Filter branches by name |
pageSize | number | — | Results per page (default: 100) |
pageNumber | number | — | Page number (default: 1) |
pacticipantName | string | Yes | Name of the pacticipant |
Parameters from the server's own tool schema.
Why contract-testing_list_branches is rated Low
This tool retrieves and lists branches for a pacticipant in PactFlow (contract testing). It performs no writes, deletes, executions, or financial operations. The filtering and pagination parameters are all query parameters, not mutation parameters. This is a standard Read operation with minimal blast radius if misused—an agent could only retrieve information that already exists.
From the tool's definition Tool description states 'Retrieve all branches' with parameters for filtering and pagination. The verb 'Retrieve' and the read-only nature of the parameters (filtering, pagination) indicate a query operation with no data modification.
Attacks that exploit this kind of access
The rule that runs contract-testing_list_branches 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_list_branches, this is the rule to start with:
contract-testing_list_branches is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect SmartBear MCP, apply this rule, and every contract-testing_list_branches call is checked against it from then on.
Questions about contract-testing_list_branches
Retrieve all branches for a given pacticipant, with optional filtering and pagination. Parameters: - pacticipantName (string) *required*: Name of the pacticipant - q (string): Filter branches by name - pageNumber (number): Page number (default: 1) - pageSize (number): Results per page (default: 100). It is categorised as a Read tool in the SmartBear MCP MCP Server, which means it retrieves data without modifying state.
contract-testing_list_branches accepts 4 parameters: q, pageSize, pageNumber, pacticipantName. Required: pacticipantName. The full parameter table on this page comes from the server's own tool schema.
Register the SmartBear MCP server in PolicyLayer and add a rule for contract-testing_list_branches: 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.
contract-testing_list_branches is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the contract-testing_list_branches 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.
Set action: deny in the PolicyLayer policy for contract-testing_list_branches. 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.
contract-testing_list_branches 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.
This server
Across the catalogue