contract-testing_list_webhooks
Retrieve all webhooks configured in the workspace. Parameters:
This record as markdown: /tools/smartbear-mcp/contract-testing-list-webhooks.md
What contract-testing_list_webhooks does on SmartBear MCP
AI agents call contract-testing_list_webhooks to retrieve information from SmartBear MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why contract-testing_list_webhooks is rated Low
This tool queries and returns existing webhook configurations without modifying, deleting, or executing them. It is a passive information retrieval operation. Severity is low because webhook configuration data, while potentially sensitive, is typically metadata without direct financial or destructive impact. Confidence is high due to clear read-only semantics in both name and description.
From the tool's definition Tool name and description indicate retrieval operation: 'list_webhooks' and 'Retrieve all webhooks configured in the workspace.' The verb 'Retrieve' and action 'list' are read-only operations with no data modification or side effects.
Attacks that exploit this kind of access
The rule that runs contract-testing_list_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_list_webhooks, this is the rule to start with:
contract-testing_list_webhooks is read-only, so it stays allowed. 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_list_webhooks call is checked against it from then on.
Questions about contract-testing_list_webhooks
Retrieve all webhooks configured in the workspace. Parameters:. It is categorised as a Read tool in the SmartBear MCP MCP Server, which means it retrieves data without modifying state.
Register the SmartBear MCP server in PolicyLayer and add a rule for contract-testing_list_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_list_webhooks is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the contract-testing_list_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_list_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_list_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.
This server
Across the catalogue