AI agents call woo_customers to retrieve information from UnClick without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
page | number | — | |
role | string | — | |
email | string | — | |
order | string | — | |
search | string | — | |
orderby | string | — | |
per_page | number | — | |
store_url | string | Yes | |
consumer_key | string | Yes | |
consumer_secret | string | Yes |
Parameters from the server's own tool schema.
This tool performs a read-only operation by listing/querying existing customer records from a WooCommerce store. It retrieves data with no side effects, making it a Read category tool. Severity is low because listing customers, while sensitive from a privacy perspective, does not pose immediate operational risk (no data modification, deletion, or financial transactions) and is typically a standard business operation.
From the tool's definition Tool name and description indicate 'List WooCommerce customers' — a retrieval operation that queries customer data without modification, deletion, or execution.
Risk signalsHigh parameter count (10 properties)
Attacks that exploit this kind of access
List WooCommerce customers. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
woo_customers accepts 10 parameters: page, role, email, order, search, orderby, per_page, store_url, consumer_key, consumer_secret. Required: store_url, consumer_key, consumer_secret. The full parameter table on this page comes from the server's own tool schema.
Register the UnClick MCP server in PolicyLayer and add a rule for woo_customers: 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 UnClick. Nothing to install.
woo_customers 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_customers 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_customers. 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_customers is provided by the UnClick MCP server (@unclick/mcp-server). 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 →