Create a new WooCommerce product attribute
AI agents use create_product_attribute 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.
Creating product attributes is a Write-class action: it adds new configuration data to the WooCommerce store but is not irreversible (attributes can be updated or removed), does not execute arbitrary code, and does not involve financial transactions.
From the tool's definition Tool name 'create_product_attribute' and description 'Create a new WooCommerce product attribute' indicate data creation. This is a reversible write operation—attributes can be modified or deleted afterward.
Attacks that exploit this kind of access
Create a new WooCommerce product attribute. 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_product_attribute: 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_product_attribute 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_product_attribute 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_product_attribute. 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_product_attribute 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 →