This record as markdown: /tools/io-github-malamutemayhem-unclick-mcp-server/woo-products.md
What woo_products does on UnClick
AI agents call woo_products to retrieve information from UnClick without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
| Parameter | Type | Required | Description |
|---|---|---|---|
id | string | — | Product ID for action='get' |
page | number | — | |
order | string | — | |
action | string | — | list or get (default: list) |
search | string | — | |
status | string | — | publish, draft, pending, private |
orderby | string | — | |
category | string | — | |
per_page | number | — | |
store_url | string | Yes | WooCommerce store URL (e.g. https://mystore.com) |
consumer_key | string | Yes | WooCommerce consumer key (ck_...) |
consumer_secret | string | Yes | WooCommerce consumer secret (cs_...) |
Parameters from the server's own tool schema.
Why woo_products is rated Low
This tool performs read-only queries against a WooCommerce store's product catalog. 'List' and 'get' are standard retrieval operations that retrieve data without any capability to create, modify, delete, or execute actions. The blast radius of misuse is minimal—an attacker could enumerate products or gather product information, but cannot alter inventory, process payments, or cause destructive changes.
From the tool's definition Tool description explicitly states 'List or get WooCommerce products' — pure retrieval operations with no modification, deletion, or side effects.
Risk signalsHigh parameter count (12 properties)
Attacks that exploit this kind of access
The rule that runs woo_products safely
PolicyLayer is an MCP gateway: it sits between your AI agents and UnClick, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For woo_products, this is the rule to start with:
woo_products is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect UnClick, apply this rule, and every woo_products call is checked against it from then on.
Questions about woo_products
List or get WooCommerce products. It is categorised as a Read tool in the UnClick MCP Server, which means it retrieves data without modifying state.
woo_products accepts 12 parameters: id, page, order, action, search, status, orderby, category, 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_products: 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_products 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_products 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_products. 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_products 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.
More on UnClick, and thousands of servers like it.
This server
Across the catalogue