contract-testing_review_pact_tests
Review Pact tests using PactFlow AI. You can provide the following inputs: (1) Pact tests to be reviewed along with metadata Parameters: - pactTests (object) *required*: Primary pact tests that needs to be refined. - code (array): Collection of source code files to analyze and extract API interac...
This record as markdown: /tools/smartbear-mcp/contract-testing-review-pact-tests.md
What contract-testing_review_pact_tests does on SmartBear MCP
AI agents invoke contract-testing_review_pact_tests to trigger actions in SmartBear MCP. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call: builds kicked off, notifications sent, workflows started.
| Parameter | Type | Required | Description |
|---|---|---|---|
code | array | — | Collection of source code files to analyze and extract API interactions from. Include client code, data models, existing tests, or any code that makes API calls |
openapi | object | — | If provided, the OpenAPI document which describes the API being tested and is accompanied by a matcher which will be used to identify the interactions in the Op |
pactTests | object | Yes | Primary pact tests that needs to be refined. |
errorMessages | array | — | Optional error output from failed contract test runs. These can be used to better understand the context or failures observed and guide the recommendations towa |
userInstructions | string | — | Optional free-form instructions that provide additional context or specify areas of focus during the refinement process of the Pact test. |
Parameters from the server's own tool schema.
Why contract-testing_review_pact_tests is rated High
The tool submits code and tests to PactFlow AI for review and refinement, which constitutes triggering an external operation rather than simply retrieving stored data. It processes arbitrary source code and pact tests through an AI system, making it an Execute-category action.
From the tool's definition 'Review Pact tests using PactFlow AI' — triggers an external AI-powered analysis operation on provided code and test inputs; not a simple read/query of stored data but an active processing/execution pipeline
Risk signalsAccepts file system path (pactTests.filename) · Accepts raw HTML/template content (pactTests.body) · Accepts freeform code/query input (code) · Accepts URL/endpoint input (openapi.remoteDocument.url) · High parameter count (25 properties)
Attacks that exploit this kind of access
The rule that runs contract-testing_review_pact_tests 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_review_pact_tests, this is the rule to start with:
contract-testing_review_pact_tests stays usable, but rate-capped: a runaway agent can't fire it dozens of times a minute. 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_review_pact_tests call is checked against it from then on.
Questions about contract-testing_review_pact_tests
Review Pact tests using PactFlow AI. You can provide the following inputs: (1) Pact tests to be reviewed along with metadata Parameters: - pactTests (object) *required*: Primary pact tests that needs to be refined. - code (array): Collection of source code files to analyze and extract API interactions from. Include client code, data models, existing tests, or any code that makes API calls - userInstructions (string): Optional free-form instructions that provide additional context or specify areas of focus during the refinement process of the Pact test. - errorMessages (array): Optional error output from failed contract test runs. These can be used to better understand the context or failures observed and guide the recommendations toward resolving specific issues. - openapi (any). It is categorised as a Execute tool in the SmartBear MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.
contract-testing_review_pact_tests accepts 5 parameters: code, openapi, pactTests, errorMessages, userInstructions. Required: pactTests. 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_review_pact_tests: 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_review_pact_tests is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.
Yes. Add a rate_limit block to the contract-testing_review_pact_tests 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_review_pact_tests. 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_review_pact_tests 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.
Across the catalogue