contract-testing_execute_webhook

Trigger a test execution of a specific webhook. Parameters: - webhookId (string) *required*: UUID of the webhook

SERVERSmartBear MCP SOURCESmartBear/smartbear-mcp

High RISK CLASS

Category Execute

Parameters 11 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-execute-webhook.md

WHAT IT DOES

What contract-testing_execute_webhook does on SmartBear MCP

AI agents invoke contract-testing_execute_webhook 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
`webhookId`	string	Yes	UUID of the webhook

Parameters from the server's own tool schema.

RISK

Why contract-testing_execute_webhook is rated High

This tool executes a webhook trigger, which runs code or operations on external systems. While labeled a 'test execution,' webhooks can perform arbitrary actions (HTTP requests, data modifications, notifications) on external services. The blast radius depends on what the webhook does, but triggering it is an active execution operation.

From the tool's definition Tool description states 'Trigger a test execution of a specific webhook' — the word 'Trigger' and 'execution' indicate this tool initiates an external operation whose effects depend on the webhook configuration and target endpoint.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

contract-testing_execute_webhook Rate-limited

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

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "contract-testing_execute_webhook": {
      "limits": [
        {
          "counter": "contract-testing_execute_webhook_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-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_execute_webhook call is checked against it from then on.

FAQ

Questions about contract-testing_execute_webhook

What does the contract-testing_execute_webhook tool do? +

Trigger a test execution of a specific webhook. Parameters: - webhookId (string) *required*: UUID of the webhook. 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.

What parameters does contract-testing_execute_webhook accept? +

contract-testing_execute_webhook accepts 1 parameter: webhookId. 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_execute_webhook? +

Register the SmartBear MCP server in PolicyLayer and add a rule for contract-testing_execute_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_execute_webhook? +

contract-testing_execute_webhook is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit contract-testing_execute_webhook? +

Yes. Add a rate_limit block to the contract-testing_execute_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_execute_webhook completely? +

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

contract-testing_execute_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 → High-risk tools on this server →

Across the catalogue

claude_execute on Claude Bridge →execute_test_case on Percepta MCP Server → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →