Part 3 of 4: The Small-Business WordPress Control Series
Begin with read access because the first goal is to understand the website, not change it. Limit the connection to the correct site and the smallest useful tool set. Review findings first, approve one low-risk change at a time, and keep security, payments, users, code, and major technical work outside the process.
In Part 2, we explained what the connection adds. Now we need to control that access before using it.
Read access and write access are different
Read tools retrieve information. They may show site details, pages, posts, comments, categories, media information, or other available records. A read-only review should not change the website.
Write tools perform actions. Depending on the connected tools and permissions, they may create a draft, edit content, publish a post, update a category, change media details, or complete another WordPress task.
WordPress.com’s current guidance says that enabling MCP access turns on both the Read and Write tool groups by default. If you want a limited first session, do not assume it is read-only. Open the MCP settings and customize the available tools before you begin.
Three controls work together
1. WordPress MCP tool settings
WordPress.com allows account-level and site-level tool controls. Account settings provide defaults. Site-level settings can create stricter rules for one website and take priority over account settings.
2. The connected WordPress user role
MCP respects WordPress user-role permissions. An administrator can normally do more than an editor, author, or contributor. Use the lowest role that still supports the approved work. Do not give broad administrator access merely to handle routine content.
3. ChatGPT app permissions and approvals
ChatGPT may show an approval card before an app action runs. The available choices can vary by action and account. App permission settings control when ChatGPT asks; they do not give the app access it did not already have.
Your operating rule should be stricter than the software’s minimum. Require approval before every website change during the first sessions, even when a setting could allow some low-risk actions automatically.
A safer setup sequence
- Confirm the exact website. Match the site name, domain, and WordPress account before reviewing content.
- Choose one site. Enable access only where it is needed instead of opening every website in the account.
- Review the user role. Use a role suited to the routine content work.
- Inspect the tool list. Separate Read tools from Write tools and disable anything outside the approved scope.
- Begin with reading. Ask for an audit, inventory, or list of findings without allowing changes.
- Approve one small edit. Review the old text, proposed text, page URL, and reason before authorizing the action.
- Verify and record. Check the saved content and public page, then write down what changed.
If the website is important to daily operations, confirm that a current backup or recovery method exists before enabling write work. A routine content process should still have a way to reverse an unwanted change.
Use this first-session instruction
You are reviewing [FULL DOMAIN].
First confirm that the connected website matches this domain.
Use read-only actions for this session. Do not create, edit, publish, delete, upload, submit, or change anything.
Review [PAGE URL] for:
1. outdated facts,
2. unclear wording,
3. weak calls to action,
4. broken or confusing internal links, and
5. missing information a customer may need.
Return the five most important findings. For each finding, show the exact page section, explain the problem in plain English, and recommend a correction.
Wait for my approval before preparing or making any change.This prompt does not create a technical permission by itself. It adds a clear instruction on top of the actual WordPress and ChatGPT access controls.
What should stay outside the routine workflow
- Plugins, themes, custom code, or databases
- DNS, domains, hosting, or server settings
- Users, roles, passwords, or security tools
- Payments, checkout rules, prices, refunds, banking, or tax settings
- Legal, privacy, medical, financial, safety, or compliance claims without qualified review
- Private customer records or other sensitive data
- Large redesigns or changes that affect many pages at once
ChatGPT may help explain a technical issue or prepare questions for a professional. That is different from authorizing it to perform the work.
How to approve a small change
Do not approve a vague instruction such as “make it better.” Ask for a change plan that contains:
- The exact site and page URL
- The current wording or block
- The proposed replacement
- The reason for the change
- Anything that will remain untouched
- The tool or action that will be used
- The verification step after saving
Then approve only the named change. If ChatGPT discovers another problem while working, it should stop and report it instead of expanding the task.
A first-session checklist
- Correct WordPress account confirmed
- Correct website and domain confirmed
- Read and Write tools reviewed
- Unneeded tools disabled
- User role checked
- No sensitive information placed in the prompt
- Read-only audit completed first
- One low-risk change selected
- Exact change approved
- Public result verified
- Change recorded
For a fuller inspection process, use the WordPress audit guide. If you want help establishing the connection and approval rules, review the guided setup service.
What comes next
Part 4 publishes next week: Your First ChatGPT WordPress Workflow. It will provide the exact prompts for reviewing a page, approving one change, verifying the result, and maintaining a simple change log.