claudeus_wp_health__run_all_tests

Run all site health tests. Execute all available health checks in parallel and return comprehensive results.

SERVERClaudeus WordPress MCP SOURCEdeus-h/claudeus-wp-mcp

High RISK CLASS

Category Execute

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/deus-h-claudeus-wp-mcp/claudeus-wp-health--run-all-tests.md

WHAT IT DOES

What claudeus_wp_health__run_all_tests does on Claudeus WordPress MCP

AI agents invoke claudeus_wp_health__run_all_tests to trigger actions in Claudeus WordPress MCP. 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.

RISK

Why claudeus_wp_health__run_all_tests is rated High

This tool executes diagnostic/health check operations on the WordPress site. While health checks are typically read-only in nature, the 'run' and 'execute' language combined with parallel execution of checks indicates active triggering of site diagnostics that could have side effects (resource consumption, external API calls, or loggin changes).

From the tool's definition Tool name contains 'run_all_tests' and description states 'Execute all available health checks in parallel' — these verbs indicate execution of operations that trigger external health check processes on the WordPress site.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs claudeus_wp_health__run_all_tests safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Claudeus WordPress MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For claudeus_wp_health__run_all_tests, this is the rule to start with:

claudeus_wp_health__run_all_tests Rate-limited

claudeus_wp_health__run_all_tests 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": {
    "claudeus_wp_health__run_all_tests": {
      "limits": [
        {
          "counter": "claudeus_wp_health__run_all_tests_rate",
          "window": "minute",
          "max": 10,
          "scope": "grant"
        }
      ]
    }
  }
}

RATE-LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Claudeus WordPress MCP, apply this rule, and every claudeus_wp_health__run_all_tests call is checked against it from then on.

FAQ

Questions about claudeus_wp_health__run_all_tests

What does the claudeus_wp_health__run_all_tests tool do? +

Run all site health tests. Execute all available health checks in parallel and return comprehensive results. It is categorised as a Execute tool in the Claudeus WordPress MCP MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on claudeus_wp_health__run_all_tests? +

Register the Claudeus WordPress MCP server in PolicyLayer and add a rule for claudeus_wp_health__run_all_tests: 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 Claudeus WordPress MCP. Nothing to install.

What risk level is claudeus_wp_health__run_all_tests? +

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

Can I rate-limit claudeus_wp_health__run_all_tests? +

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

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

claudeus_wp_health__run_all_tests is provided by the Claudeus WordPress MCP server (deus-h/claudeus-wp-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Claudeus WordPress, and thousands of servers like it.

This server

All 145 Claudeus WordPress tools → High-risk tools on this server →

Across the catalogue

run on 0sec →shortcuts_run on Apple Apps MCP →run_emba_scan on EMBA-MCP → All high-risk MCP tools → The MCP Attack Database →

Guides

Govern code and CI agents →Agent sandbox →Least privilege for MCP →