List webhooks. Use perPage and page parameters to control pagination.
AI agents call woo_webhooks_list to retrieve information from Woocommerce without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool retrieves and queries webhook configuration data without side effects. It is a standard list/read operation that returns existing webhook records. No data is created, modified, deleted, or executed. The severity is low as it only exposes configuration metadata that may have limited sensitive information depending on webhook contents.
From the tool's definition Tool name 'woo_webhooks_list' and description 'List webhooks' indicate a retrieval operation with pagination parameters (perPage, page) but no modification, deletion, or execution capability.
Attacks that exploit this kind of access
List webhooks. Use perPage and page parameters to control pagination. It is categorised as a Read tool in the Woocommerce MCP Server, which means it retrieves data without modifying state.
Register the Woocommerce MCP server in PolicyLayer and add a rule for woo_webhooks_list: 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 Woocommerce. Nothing to install.
woo_webhooks_list 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 woo_webhooks_list 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 woo_webhooks_list. 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.
woo_webhooks_list is provided by the Woocommerce MCP server (@lockon0927/woocommerce-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →