wordpress_wc_get_orders
AI agents call wordpress_wc_get_orders to retrieve information from WordPress MCP Server without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
WooCommerce order retrieval is fundamentally a read operation that queries and returns order data without modifying state. No side effects or data mutations are implied by the function signature. Low severity because order data access alone does not enable destructive, financial, or execute capabilities on its own—though the sensitivity of order data (customer PII, payment info) warrants noting.
From the tool's definition Tool name 'wordpress_wc_get_orders' indicates retrieval of WooCommerce orders (wc_get_orders follows WordPress/WooCommerce naming conventions for getter/retrieval functions).
Attacks that exploit this kind of access
wordpress_wc_get_orders. It is categorised as a Read tool in the WordPress MCP Server MCP Server, which means it retrieves data without modifying state.
Register the WordPress MCP Server MCP server in PolicyLayer and add a rule for wordpress_wc_get_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 WordPress MCP Server. Nothing to install.
wordpress_wc_get_orders 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 wordpress_wc_get_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 wordpress_wc_get_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.
wordpress_wc_get_orders is provided by the WordPress MCP Server MCP server (tonypepperwidow123-blip/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 →