contract-testing_test_execute_webhooks
Trigger a test execution of all matching webhooks without a real event. Parameters:
This record as markdown: /tools/smartbear-mcp/contract-testing-test-execute-webhooks.md
What contract-testing_test_execute_webhooks does on SmartBear MCP
AI agents invoke contract-testing_test_execute_webhooks 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.
Why contract-testing_test_execute_webhooks is rated High
The tool explicitly triggers an execution of webhooks, causing external HTTP calls or operations to be fired against configured endpoints. This is an Execute-category action as it runs external operations whose effects depend on the configured webhooks. Severity is medium since it fires test webhook calls that could affect downstream systems, but is scoped to test/simulation mode rather than real events.
From the tool's definition Trigger a test execution of all matching webhooks without a real event
Attacks that exploit this kind of access
The rule that runs contract-testing_test_execute_webhooks 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_test_execute_webhooks, this is the rule to start with:
contract-testing_test_execute_webhooks 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_test_execute_webhooks call is checked against it from then on.
Questions about contract-testing_test_execute_webhooks
Trigger a test execution of all matching webhooks without a real event. Parameters:. 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.
Register the SmartBear MCP server in PolicyLayer and add a rule for contract-testing_test_execute_webhooks: 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_test_execute_webhooks 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_test_execute_webhooks 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_test_execute_webhooks. 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_test_execute_webhooks 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