contract-testing_delete_integration
Delete a specific consumer-provider integration. Parameters: - providerName (string) *required*: Name of the provider - consumerName (string) *required*: Name of the consumer
This record as markdown: /tools/smartbear-mcp/contract-testing-delete-integration.md
What contract-testing_delete_integration does on SmartBear MCP
AI agents call contract-testing_delete_integration to permanently remove resources in SmartBear MCP, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
consumerName | string | Yes | Name of the consumer |
providerName | string | Yes | Name of the provider |
Parameters from the server's own tool schema.
Why contract-testing_delete_integration is rated Critical
The tool performs an irreversible deletion operation on a consumer-provider integration. Deletion cannot be undone without manual restoration. While not a direct security compromise, deleting integrations could disrupt API communication flows, break dependent services, or cause operational downtime. This fits the Destructive category as the highest applicable severity.
From the tool's definition Tool name contains 'delete' and description states 'Delete a specific consumer-provider integration' — this operation irreversibly removes an integration configuration.
Attacks that exploit this kind of access
The rule that runs contract-testing_delete_integration 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_delete_integration, this is the rule to start with:
contract-testing_delete_integration is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect SmartBear MCP, apply this rule, and every contract-testing_delete_integration call is checked against it from then on.
Questions about contract-testing_delete_integration
Delete a specific consumer-provider integration. Parameters: - providerName (string) *required*: Name of the provider - consumerName (string) *required*: Name of the consumer. It is categorised as a Destructive tool in the SmartBear MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
contract-testing_delete_integration accepts 2 parameters: consumerName, providerName. Required: consumerName, providerName. 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_delete_integration: 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_delete_integration is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the contract-testing_delete_integration 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_delete_integration. 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_delete_integration 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