By Fahad Murtaza · Published · Updated
Read WooCommerce payment gateways and store status safely
“Why is checkout slow?” and “which payment methods are live?” are good questions for an agent, but the answers sit next to API keys. WP MCP Pro reads both with every secret masked, so no credential reaches the model.
What you need
- WP MCP Pro, connected to your AI client, and WooCommerce active.
- A user with
manage_woocommerce.
Audit your gateways
› Which payment gateways are enabled, in what order, and are any in test mode?
The agent calls woo-read with op gateways.list (or gateways.get for one).
Every field named like a key, secret, password, token, signature or credential,
and every password-type field, comes back masked.
Change a gateway, not its secrets
› Rename "Direct bank transfer" to "Bank transfer (2 to 3 days)" and move it last.
gateways.update changes the enabled flag, title, description, order and
non-secret settings. Secret fields are refused outright: set credentials in the
WooCommerce admin screen. Each write is snapshotted as the one option it
changes, and an order change travels on its own, so every undo point covers
exactly what its write touched. Restoring a gateway snapshot takes
manage_woocommerce, because the snapshot holds the gateway’s secrets even
though they are never shown.
Read the system status report
› Check the WooCommerce system status for anything that needs attention.
system-status.get returns the report by section (environment, database,
active plugins, theme, settings, security) with secret-like values masked
wherever they appear, since extensions can add to the report.
Run a maintenance tool
› Clear the WooCommerce transients.
system-status.tools lists the tools and says which ones WP MCP runs and which
need confirm: true. system-status.run-tool runs an allowlisted one, such as
clearing transients or regenerating lookup tables. These rebuild derived data,
so they are not snapshotted, and every run says why it cannot be rolled back.
Tools that change roles, pages, tax rates or the database schema are refused.
Common questions
Can an AI agent see my WooCommerce payment gateway API keys?
No. Fields named like a key, secret, password, token, signature or credential, and every password-type field, come back masked from gateways.list and gateways.get, so no credential reaches the model.
Can the agent change payment gateway settings?
Yes, but not secrets. gateways.update changes the enabled flag, title, description, order and non-secret settings. Secret fields are refused, so set credentials in the WooCommerce admin screen.
What permission is needed to audit gateways and system status?
The connected user needs manage_woocommerce. Restoring a gateway snapshot needs it too, because the snapshot holds the gateway's secrets even though they are never shown.
Is the WooCommerce system status report masked as well?
Yes. system-status.get returns the report by section (environment, database, active plugins, theme, settings, security) with secret-like values masked wherever they appear, including values added by extensions.
Can the AI agent run WooCommerce maintenance tools such as clearing transients?
Yes, for allowlisted tools. system-status.tools lists them and which need confirm set to true, and system-status.run-tool runs one. Tools that change roles, pages, tax rates or the database schema are refused.
Can I roll back a maintenance tool run?
No. These tools rebuild derived data, so they are not snapshotted, and each run states why it cannot be rolled back. Gateway setting changes, by contrast, are snapshotted and can be undone.
All WP MCP guides, or see every plugin integration. Topic: WooCommerce.