run_system_status_tool · WooCommerce MCP Server MCP

WHAT IT DOES

What run_system_status_tool does on WooCommerce MCP Server

AI agents invoke run_system_status_tool to trigger actions in WooCommerce MCP Server. What it does depends on the arguments the agent supplies, and its effects often reach beyond the immediate call — builds kicked off, notifications sent, workflows started.

WHY IT NEEDS A POLICY

Why run_system_status_tool needs a policy

The tool name starts with 'run_' and the description says 'Execute a specific system status tool', indicating it actively runs/triggers an operation. System status tools in WooCommerce can perform actions like clearing caches, running scheduled tasks, or resetting data. This goes beyond a simple read, falling into Execute territory.

From the tool's definition 'Execute a specific system status tool' — the word 'Execute' and 'run_' prefix indicate this triggers an external operation rather than just reading data

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

run_system_status_tool Rate-limited

run_system_status_tool stays usable, but rate-capped — a runaway agent can't fire it dozens of times a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "run_system_status_tool": {
      "limits": [
        {
          "counter": "run_system_status_tool_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL →

Instant setup, no code required.

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

FAQ

Questions about run_system_status_tool

What does the run_system_status_tool tool do? +

Execute a specific system status tool. It is categorised as a Execute tool in the WooCommerce MCP Server MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on run_system_status_tool? +

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

What risk level is run_system_status_tool? +

run_system_status_tool is a Execute tool with high risk. Execute tools should be rate-limited and have argument validation enabled.

Can I rate-limit run_system_status_tool? +

Yes. Add a rate_limit block to the run_system_status_tool 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 run_system_status_tool completely? +

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

run_system_status_tool is provided by the WooCommerce MCP Server MCP server (lord-dubious/woocommerce-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.