contract-testing_matrix
Retrieve the comprehensive contract verification matrix that shows the relationship between consumer and provider versions, their associated pact files, and verification results stored in the Pact Broker or Pactflow. The matrix provides detailed visibility into which consumer and provider version...
This record as markdown: /tools/smartbear-mcp/contract-testing-matrix.md
What contract-testing_matrix does on SmartBear MCP
AI agents call contract-testing_matrix 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 | array | Yes | |
limit | number | — | The limit on the number of results to return (1-1000, default: 100) |
latestby | string | — | This property removes the rows for the overridden pacts/verifications from the results. The options are cvp (show only the latest row for each consumer version |
Parameters from the server's own tool schema.
Why contract-testing_matrix is rated Low
This tool retrieves and queries contract testing verification results from Pact Broker or Pactflow. It has no side effects—it only reads existing verification data and relationship matrices. The parameter 'latestby' filters results but does not modify underlying data. This is a pure Read operation: no data is created, modified, deleted, or financial operations are performed.
From the tool's definition Tool name contains 'matrix' and description states 'Retrieve the comprehensive contract verification matrix' and 'provides detailed visibility into which consumer and provider versions have been successfully verified.' The action is retrieval of verification…
Risk signalsHigh parameter count (10 properties)
Attacks that exploit this kind of access
The rule that runs contract-testing_matrix 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_matrix, this is the rule to start with:
contract-testing_matrix 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_matrix call is checked against it from then on.
Questions about contract-testing_matrix
Retrieve the comprehensive contract verification matrix that shows the relationship between consumer and provider versions, their associated pact files, and verification results stored in the Pact Broker or Pactflow. The matrix provides detailed visibility into which consumer and provider versions have been successfully verified against each other, and highlights failures with detailed information about the cause. Parameters: - latestby (string): This property removes the rows for the overridden pacts/verifications from the results. The options are cvp (show only the latest row for each consumer version and provider) and cvpv (show only the latest row each consumer version and provider version). For a can-i-deploy query with one selector, it should be set to cvp. For a can-i-deploy query with two selectors, it should be set to cvpv. - limit (number): The limit on the number of results to return (1-1000, default: 100) (default: 100) - q (array) *required* Use Cases: 1. Quickly identify which consumer and provider version combinations have passed or failed verification. 2. Diagnose and investigate why a particular consumer-provider verification failed. 3. Visualize the overall contract compatibility across two pacticipants / services. 4. Perform advanced queries using selectors to understand compatibility within specific branches, environments, or version ranges. 5. Support informed deployment decisions by answering 'can I deploy version X of this service to production?' 6. Expose contract verification details to non-frequent API users in a more accessible format. It is categorised as a Read tool in the SmartBear MCP MCP Server, which means it retrieves data without modifying state.
contract-testing_matrix accepts 3 parameters: q, limit, latestby. Required: q. 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_matrix: 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_matrix 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_matrix 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_matrix. 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_matrix 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