WordPress MCP Security Checklist: 12 Controls Before AI Site Access
A WordPress MCP connection exposes real operations to an AI client. Protect a production site with a checklist covering access, tool selection, change approval, credential storage and incident response.
Identity and authorization controls
- Use HTTPS for WordPress and remote connection endpoints.
- Choose a named WordPress account dedicated to the integration rather than sharing a personal administrator login.
- Grant the least WordPress role and capabilities compatible with the task.
- Confirm the exact site URL and authenticated user at the beginning of an operation.
Authenticated access is not universal permission. Plugins can register permission callbacks on their REST routes, and WordPress capabilities still control whether the request succeeds.
Scope and tool exposure
- Discover the actual installed REST routes before enabling a workflow.
- Separate read-only inspection from production edits and destructive actions.
- Use a staging site and test item for the first write attempt.
- Require a human-approved target ID, field set and intended publication state for sensitive changes.
An MCP bridge should not be described as capable of operating every WordPress dashboard feature. An unregistered or blocked REST endpoint cannot be made available by wording a prompt differently.
Operational safeguards
- Store Application Passwords and OAuth credentials in appropriate secure stores; never paste them into public prompts or tickets.
- Revoke credentials and sessions that are no longer needed.
- Retain a change record: who requested the action, which site and item were affected, and what the API reported.
- Verify both the REST read-back and the rendered public outcome; maintain recovery and backup procedures for important content.
Keep an incident path ready: disable connector access, rotate relevant credentials, check logs and restore from a verified backup if an erroneous change reaches production.
Where a commercial agency needs extra controls
Agencies should separate client site inventories and permissions. The staff member approving a change should be identifiable; prompt text is not a substitute for a client approval agreement. Record which APIs can touch customer records, financial data or memberships before authorizing access.
Review WPBridge Studio security boundaries, agency workflow guidance and commercial licensing terms. The commercial enquiry does not waive security responsibilities or permit redistribution by default.
Frequently asked questions
Does OAuth replace WordPress permissions?
No. Client authorization and site-level authorization serve different purposes.
Should an AI connector run as Administrator?
Only when a verified operation requires that capability and the site owner explicitly authorizes it.
Is a successful tool call proof that the website is safe?
No. Access must be constrained and changes verified; security is an ongoing operational process.
Related WordPress AI resources
See product features, documentation and technical support. Follow authorized WordPress access and verify any production change.