Create a new customer
AI agents use create_customer to create or update resources in WooCommerce MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your WooCommerce MCP Server environment.
This tool creates and persists new customer data in the store (name, email, address, etc.), modifying the customer database reversibly. It does not execute arbitrary code, delete data, or move money, making it a Write operation. Severity is medium because malicious customer creation could lead to spam accounts, fraudulent registrations, or data pollution, but the action is reversible (customers can be deleted).
From the tool's definition Tool name 'create_customer' and description 'Create a new customer' indicate data creation. This adds a new customer record to the WooCommerce store.
Attacks that exploit this kind of access
Create a new customer. It is categorised as a Write tool in the WooCommerce MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the WooCommerce MCP Server MCP server in PolicyLayer and add a rule for create_customer: 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.
create_customer is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the create_customer 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 create_customer. 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.
create_customer is provided by the WooCommerce MCP Server MCP server (kenan7/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 →