Retrieve a list of customers from WooCommerce
AI agents call get_customers to retrieve information from WooCommerce MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool performs a read-only query to fetch customer data. It does not modify, delete, or trigger external actions. The 'get' operation and 'retrieve' verb confirm it is a Read category tool. Severity is low because customer list retrieval has minimal risk when misused by an AI agent — it exposes existing customer data but does not modify it or cause financial harm.
From the tool's definition Tool name is 'get_customers' and description states 'Retrieve a list of customers from WooCommerce' — a pure data retrieval operation with no side effects.
Attacks that exploit this kind of access
Retrieve a list of customers from WooCommerce. It is categorised as a Read tool in the WooCommerce MCP Server MCP Server, which means it retrieves data without modifying state.
Register the WooCommerce MCP Server MCP server in PolicyLayer and add a rule for get_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 WooCommerce MCP Server. Nothing to install.
get_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 get_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 get_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.
get_customers is provided by the WooCommerce MCP Server MCP server (lord-dubious/woocommerce-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 →