Check backups, security, and cache status with your AI agent

Before an agent changes a site, it helps to know whether that site has a recent backup, what security is switched on, and what is caching the pages. WP MCP reads that from the plugins you already run, free, and never returns their credentials.

What you need

• WP MCP installed and connected to your AI client.
• Any of UpdraftPlus, Duplicator, Solid Security, MonsterInsights or W3 Total Cache. Each op is on the theme-read pair, runs at manage_options, and answers <plugin>_inactive cleanly when its plugin is not active.

Backups

› When did this site last back up, did it include the database, and is it going offsite?

get-updraftplus-status reports the last backup and the components it covered, the files and database schedules and retention, and the remote storage services by id only. get-duplicator-status lists Duplicator packages newest first and the last completed build. Storage keys, tokens, backup file names and archive names are never read.

Security

› Which Solid Security modules are on, when was the last scan, and how many lockouts are active?

get-solid-security-status returns enabled modules, the last scan’s result level and time, and counts of known vulnerabilities, lockouts and bans. No IP, host or user column is read, and scanner and API keys are never returned.

Analytics setup

› Is MonsterInsights connected, and to which GA4 property?

get-monsterinsights-status reports the connection mode, the public GA4 measurement id and view name, and allowlisted tracking settings. Tokens, site keys and secrets stay out.

Cache

› Which W3 Total Cache caches are on? Then purge everything, the new homepage is live.

get-w3tc-status shows which caches are enabled and with which engine. purge-w3tc-cache on theme-write empties every cache through the plugin’s own purge-all. A purge is not a content write, so it is not undoable: it is not snapshotted, the response says recoverable: false, and it needs confirm: true.

A second safety line

Every one of these answers is built from allowlisted fields, and then passed through a redaction step that masks any secret-shaped key that might still slip in.