admin_site_health

Prüft den WordPress Site Health Status (Security, Performance)

SERVERWordPress MCP Server SOURCEc-sakel/wp-mcp-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/c-sakel-wp-mcp-server/admin-site-health.md

WHAT IT DOES

What admin_site_health does on WordPress MCP Server

AI agents call admin_site_health to retrieve information from WordPress MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why admin_site_health is rated Low

This tool performs a health check and status inspection of WordPress security and performance. It retrieves diagnostic information but does not execute commands, modify content, delete data, or commit financial actions. It is purely informational and read-only in nature, making it a Read category tool with low severity risk.

From the tool's definition Tool name 'admin_site_health' and description 'Prüft den WordPress Site Health Status (Security, Performance)' indicate a diagnostic/monitoring function that checks and reports on site health metrics without modifying anything.

Risk signalsAdmin/system-level operation

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs admin_site_health safely

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

admin_site_health Allowed

admin_site_health is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "admin_site_health": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about admin_site_health

What does the admin_site_health tool do? +

Prüft den WordPress Site Health Status (Security, Performance). It is categorised as a Read tool in the WordPress MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on admin_site_health? +

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

admin_site_health is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit admin_site_health? +

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

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

admin_site_health is provided by the WordPress MCP Server MCP server (c-sakel/wp-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on WordPress MCP Server, and thousands of servers like it.

This server

All 192 WordPress MCP Server tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →