mcp_get_plugins_health
Get plugin health status and available updates
This record as markdown: /tools/io-github-cvrt-jh-wordpress-mcp/mcp-get-plugins-health.md
What mcp_get_plugins_health does on Wordpress
AI agents call mcp_get_plugins_health to retrieve information from Wordpress without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why mcp_get_plugins_health is rated Low
This tool queries plugin status and available update information. It retrieves data about the state of installed plugins and checks for updates, but does not install, activate, deactivate, or modify any plugins. No side effects occur from calling this tool. The severity is low because the information revealed is already accessible to site administrators and does not enable harmful actions on its own.
From the tool's definition Tool name contains 'get' and description states 'Get plugin health status and available updates' - purely retrieves information without modifying data.
Attacks that exploit this kind of access
The rule that runs mcp_get_plugins_health safely
PolicyLayer is an MCP gateway: it sits between your AI agents and Wordpress, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For mcp_get_plugins_health, this is the rule to start with:
mcp_get_plugins_health is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Wordpress, apply this rule, and every mcp_get_plugins_health call is checked against it from then on.
Questions about mcp_get_plugins_health
Get plugin health status and available updates. It is categorised as a Read tool in the Wordpress MCP Server, which means it retrieves data without modifying state.
Register the Wordpress MCP server in PolicyLayer and add a rule for mcp_get_plugins_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. Nothing to install.
mcp_get_plugins_health 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 mcp_get_plugins_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.
Set action: deny in the PolicyLayer policy for mcp_get_plugins_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.
mcp_get_plugins_health is provided by the Wordpress MCP server (@cavort-it-systems/wordpress-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Wordpress, and thousands of servers like it.
This server
Across the catalogue