mcp_update_core

Update WordPress to the latest version. Returns { updated: false, message } when already up to date.

SERVERWordpress SOURCE@cavort-it-systems/wordpress-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/io-github-cvrt-jh-wordpress-mcp/mcp-update-core.md

WHAT IT DOES

What mcp_update_core does on Wordpress

AI agents invoke mcp_update_core to trigger actions in Wordpress. 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 mcp_update_core is rated High

Triggers a core system update, an irreversible external operation affecting the entire WordPress installation.

From the tool's definition Update WordPress to the latest version

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs mcp_update_core 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_update_core, this is the rule to start with:

mcp_update_core Rate-limited

mcp_update_core 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": {
    "mcp_update_core": {
      "limits": [
        {
          "counter": "mcp_update_core_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 Wordpress, apply this rule, and every mcp_update_core call is checked against it from then on.

FAQ

Questions about mcp_update_core

What does the mcp_update_core tool do? +

Update WordPress to the latest version. Returns { updated: false, message } when already up to date. It is categorised as a Execute tool in the Wordpress MCP Server, which means it can trigger actions or run processes. Use rate limits and argument validation.

How do I enforce a policy on mcp_update_core? +

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

What risk level is mcp_update_core? +

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

Can I rate-limit mcp_update_core? +

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

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

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

KEEP EXPLORING

More on Wordpress, and thousands of servers like it.

This server

All 314 Wordpress tools → High-risk tools on this server →

Across the catalogue

All high-risk MCP tools → The MCP Attack Database →

Guides

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