AI agents use woo_orders to create or update resources in UnClick — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your UnClick environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | — | Order ID for action='get' |
page | number | — | |
after | string | — | ISO 8601 date for orders after this date |
order | object | — | Order object for action='create' |
action | string | — | list, get, or create (default: list) |
before | string | — | |
status | string | — | pending, processing, completed, refunded, etc. |
customer | number | — | Filter by customer ID |
per_page | number | — | |
store_url | string | Yes | |
consumer_key | string | Yes | |
consumer_secret | string | Yes |
Parameters from the server's own tool schema.
While the tool includes read operations (list, get), the presence of 'create' elevates it to Write category. Creating orders is a reversible modification that commits financial/commercial transactions in an e-commerce system, making it high severity due to potential for fraudulent orders, inventory issues, or financial exposure if an agent misuses this capability.
From the tool's definition Tool description states 'List, get, or create WooCommerce orders.' The 'create' capability indicates the tool can generate new orders, which modifies data in the WooCommerce system.
Risk signalsHigh parameter count (12 properties)
Attacks that exploit this kind of access
List, get, or create WooCommerce orders. It is categorised as a Write tool in the UnClick MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
woo_orders accepts 12 parameters: id, page, after, order, action, before, status, customer, 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_orders: 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_orders 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 woo_orders 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_orders. 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_orders 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 →