contract-testing_update_webhook

SERVERSmartBear MCP SOURCESmartBear/smartbear-mcp

Medium RISK CLASS

Category Write

Parameters 81 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/smartbear-mcp/contract-testing-update-webhook.md

WHAT IT DOES

What contract-testing_update_webhook does on SmartBear MCP

AI agents use contract-testing_update_webhook to create or update resources in SmartBear MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your SmartBear MCP environment.

Parameter	Type	Required	Description
`events`	array	—	Events that trigger this webhook
`enabled`	boolean	—	Whether the webhook is enabled
`request`	object	—	HTTP request to send when triggered
`consumer`	object	—	Restrict to a specific consumer
`provider`	object	—	Restrict to a specific provider
`teamUuid`	object	—	UUID of the owning team
`webhookId`	string	Yes	UUID of the webhook to update
`description`	string	—	Human-readable description

Parameters from the server's own tool schema.

RISK

Why contract-testing_update_webhook is rated Medium

This tool modifies webhook configuration reversibly—it updates settings without permanently destroying data. The blast radius is medium: a compromised agent could redirect webhooks to attacker-controlled endpoints, exfiltrate data, or disable critical integrations, but the changes are not destructive and can be reverted.

From the tool's definition Tool name contains 'update' and description states 'Update an existing webhook's configuration.' Parameters allow modification of webhook behavior including events, request details, consumer/provider restrictions, and enabled status.

Risk signalsAccepts URL/endpoint input (request.url) · Accepts raw HTML/template content (request.body) · Handles credentials or secrets (request.password) · High parameter count (15 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs contract-testing_update_webhook 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_update_webhook, this is the rule to start with:

contract-testing_update_webhook Rate-limited

contract-testing_update_webhook stays usable, but capped: an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "contract-testing_update_webhook": {
      "limits": [
        {
          "counter": "contract-testing_update_webhook_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect SmartBear MCP, apply this rule, and every contract-testing_update_webhook call is checked against it from then on.

FAQ

Questions about contract-testing_update_webhook

What does the contract-testing_update_webhook tool do? +

Update an existing webhook's configuration. Parameters: - webhookId (string) *required*: UUID of the webhook to update - description (string): Human-readable description - events (array): Events that trigger this webhook - request (object): HTTP request to send when triggered - consumer (object): Restrict to a specific consumer - provider (object): Restrict to a specific provider - enabled (boolean): Whether the webhook is enabled - teamUuid (string): UUID of the owning team. 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.

What parameters does contract-testing_update_webhook accept? +

contract-testing_update_webhook accepts 8 parameters: events, enabled, request, consumer, provider, teamUuid, webhookId, description. Required: webhookId. The full parameter table on this page comes from the server's own tool schema.

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

Register the SmartBear MCP server in PolicyLayer and add a rule for contract-testing_update_webhook: 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.

What risk level is contract-testing_update_webhook? +

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

Can I rate-limit contract-testing_update_webhook? +

Yes. Add a rate_limit block to the contract-testing_update_webhook 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.

How do I block contract-testing_update_webhook completely? +

Set action: deny in the PolicyLayer policy for contract-testing_update_webhook. 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_update_webhook? +

contract-testing_update_webhook 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.

KEEP EXPLORING

More on SmartBear, and thousands of servers like it.

This server

All 240 SmartBear tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP →team_manager_update_budget on Team Manager MCP → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →