mcp_check_updates

Force a check for WordPress core, plugin, and theme updates. Returns { core: new core version or null, plugins: count, themes: count }.

SERVERWordpress SOURCE@cavort-it-systems/wordpress-mcp

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/io-github-cvrt-jh-wordpress-mcp/mcp-check-updates.md

WHAT IT DOES

What mcp_check_updates does on Wordpress

AI agents call mcp_check_updates 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.

RISK

Why mcp_check_updates is rated Low

Tool queries update availability without modifying, installing, or triggering updates.

From the tool's definition Force check for WordPress core, plugin, theme updates. Returns version counts.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

mcp_check_updates Allowed

mcp_check_updates 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": {
    "mcp_check_updates": {}
  }
}

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

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

FAQ

Questions about mcp_check_updates

What does the mcp_check_updates tool do? +

Force a check for WordPress core, plugin, and theme updates. Returns { core: new core version or null, plugins: count, themes: count }. It is categorised as a Read tool in the Wordpress MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on mcp_check_updates? +

Register the Wordpress MCP server in PolicyLayer and add a rule for mcp_check_updates: 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_check_updates? +

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

Can I rate-limit mcp_check_updates? +

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

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

mcp_check_updates 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 →

Across the catalogue

The MCP Attack Database →

Guides

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