AI agents call wp_core_check_update to retrieve information from Wp Cli without modifying anything — typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
This tool only retrieves and reports information about available WordPress updates; it does not install, apply, or modify any systems. It is purely informational and read-only, comparable to a version check or status query. No data is created, modified, deleted, or executed. Severity is low because even if misused by an agent, the worst outcome is displaying outdated or irrelevant update information.
From the tool's definition Tool name 'wp_core_check_update' and description 'Check if WordPress core updates are available. Returns a list of available versions with download URLs.' indicate a query/retrieval operation with no side effects.
Attacks that exploit this kind of access
Check if WordPress core updates are available. Returns a list of available versions with download URLs. Use this before running updates to see what. It is categorised as a Read tool in the Wp Cli MCP Server, which means it retrieves data without modifying state.
Register the Wp Cli MCP server in PolicyLayer and add a rule for wp_core_check_update: 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 Wp Cli. Nothing to install.
wp_core_check_update 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 wp_core_check_update 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 wp_core_check_update. 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.
wp_core_check_update is provided by the Wp Cli MCP server (mvtandas/wp-cli-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →