Medium Risk

contract-testing_generate_pact_tests

Generate Pact tests using PactFlow AI. You can provide one or more of the following input types: (1) request/response pairs for specific interactions, (2) code files to analyze and extract interactions from, and/or (3) OpenAPI document to generate tests for specific endpoints. When providing an O...

Accepts file system path (requestResponse.request.filename); Accepts raw HTML/template content (requestResponse.request.body); Accepts freeform code/query input (code); Accepts URL/endpoint input (openapi.remoteDocument.url); High parameter count (34 properties); Single-target operation

Part of the SmartBear MCP MCP server. Enforce policies on this tool with Intercept, the open-source MCP proxy.

AI agents use contract-testing_generate_pact_tests to create or modify resources in SmartBear MCP. Write operations carry medium risk because an autonomous agent could trigger bulk unintended modifications. Rate limits prevent a single agent session from making hundreds of changes in rapid succession. Argument validation ensures the agent passes expected values.

Without a policy, an AI agent could call contract-testing_generate_pact_tests repeatedly, creating or modifying resources faster than any human could review. Intercept's rate limiting ensures write operations happen at a controlled pace, and argument validation catches malformed or unexpected inputs before they reach SmartBear MCP.

Write tools can modify data. A rate limit prevents runaway bulk operations from AI agents.

smartbear-mcp.yaml
tools:
  contract-testing_generate_pact_tests:
    rules:
      - action: allow
        rate_limit:
          max: 30
          window: 60

See the full SmartBear MCP policy for all 243 tools.

Tool Name contract-testing_generate_pact_tests
Category Write
Risk Level Medium

View all 243 tools →

Agents calling write-class tools like contract-testing_generate_pact_tests have been implicated in these attack patterns. Read the full case and prevention policy for each:

Browse the full MCP Attack Database →

Other tools in the Write risk category across the catalogue. The same policy patterns (rate-limit, validate) apply to each.

What does the contract-testing_generate_pact_tests tool do? +

Generate Pact tests using PactFlow AI. You can provide one or more of the following input types: (1) request/response pairs for specific interactions, (2) code files to analyze and extract interactions from, and/or (3) OpenAPI document to generate tests for specific endpoints. When providing an OpenAPI document, a matcher is required to specify which endpoints to generate tests for. **Parameters:** - language (enum): Target language for the generated Pact tests. If not provided, will be inferred from other inputs. - requestResponse (object): Direct request/response pair for a specific interaction. Use this when you have concrete examples of API requests and responses - 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 (any) - additionalInstructions (string): Optional free-form instructions to guide the generation process (e.g., 'Focus on error scenarios', 'Include authentication headers', 'Use specific test framework patterns') - testTemplate (object): Optional test template to use as a basis for generation. Helps ensure generated tests follow your specific patterns, frameworks, and coding standards. It is categorised as a Write tool in the SmartBear MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on contract-testing_generate_pact_tests? +

Add a rule in your Intercept YAML policy under the tools section for contract-testing_generate_pact_tests. You can allow, deny, rate-limit, or validate arguments. Then run Intercept as a proxy in front of the SmartBear MCP MCP server.

What risk level is contract-testing_generate_pact_tests? +

contract-testing_generate_pact_tests is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit contract-testing_generate_pact_tests? +

Yes. Add a rate_limit block to the contract-testing_generate_pact_tests rule in your Intercept 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_generate_pact_tests completely? +

Set action: deny in the Intercept policy for contract-testing_generate_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.

What MCP server provides contract-testing_generate_pact_tests? +

contract-testing_generate_pact_tests is provided by the SmartBear MCP MCP server (@smartbear/mcp). Intercept sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Let agents act without letting them run wild.

Deterministic policy on every MCP tool call. Per-identity grants. Full audit log.

// GET IN TOUCH

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

Message sent.

We'll get back to you soon.