wordpress_wc_update_order_status · WordPress MCP Server MCP

WHAT IT DOES

What wordpress_wc_update_order_status does on WordPress MCP Server

AI agents use wordpress_wc_update_order_status to create or update resources in WordPress MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your WordPress MCP Server environment.

WHY IT NEEDS A POLICY

Why wordpress_wc_update_order_status needs a policy

The tool name indicates it updates the status of a WooCommerce order (e.g., pending, processing, completed, refunded). This is a Write operation as order status changes are reversible. However, severity is high because changing order status (e.g., marking as refunded or cancelled) can have significant business and financial implications, even if it doesn't directly move money.

From the tool's definition Tool name: wordpress_wc_update_order_status — 'update' and 'order_status' suggest modifying a WooCommerce order's status field. Description is empty.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

wordpress_wc_update_order_status Rate-limited

wordpress_wc_update_order_status stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "wordpress_wc_update_order_status": {
      "limits": [
        {
          "counter": "wordpress_wc_update_order_status_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches WordPress MCP Server, so you can run agents against it safely.

FAQ

Questions about wordpress_wc_update_order_status

What does the wordpress_wc_update_order_status tool do? +

wordpress_wc_update_order_status. It is categorised as a Write tool in the WordPress MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on wordpress_wc_update_order_status? +

Register the WordPress MCP Server MCP server in PolicyLayer and add a rule for wordpress_wc_update_order_status: 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.

What risk level is wordpress_wc_update_order_status? +

wordpress_wc_update_order_status is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit wordpress_wc_update_order_status? +

Yes. Add a rate_limit block to the wordpress_wc_update_order_status 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.

How do I block wordpress_wc_update_order_status completely? +

Set action: deny in the PolicyLayer policy for wordpress_wc_update_order_status. 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.

What MCP server provides wordpress_wc_update_order_status? +

wordpress_wc_update_order_status 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.