Is it safe to let Claude or ChatGPT edit WordPress?

After you install AlphaBridge, it only reads. Assistants see content, media, terms, comments, settings and the structure of the site. With Pro they also read users and, with WooCommerce, the shop's data. Every tool that creates, changes or deletes is refused. So are tools that read code, files or the database.

An administrator switches on “Write access for AI assistants” at the top of Settings → AlphaBridge MCP. The switch holds for every connection: Claude, ChatGPT, Cursor and all others.

Before it goes on, the administrator ticks a box under a notice. The notice says that changes then take effect immediately and can be destructive. Switching on is at the owner's own risk. The box also confirms that a current backup exists. The plugin records who switched it on and when.

Switching on turns every tool on. Under Fine-tuning you then switch off single tools or groups you do not need. Switching write access on again later turns every tool back on. One click switches write access off.

Each connection belongs to one WordPress user. Every tool checks that user's capability for the very post, file or term in question. What the user may not do, the AI cannot do either.

Claude and ChatGPT connect through a consent screen on your own site. The connection then acts as the account that approved it. By default, only administrators may approve connections.

Each connection also has an access level. It narrows what the user may do and never widens it. You pick it on the consent screen before you approve.

• With read-only access, the connection sees what the account may see and changes nothing.
• With content-only access, it also changes or deletes posts, pages, media, terms and comments. Theme and plugin files and site settings are out of its reach.
• With Pro, content-only access also blocks the tools that change the database.
• With full access, it may do everything the account may do with the tools switched on.

Cursor, Claude Code and scripts connect with a token instead. An administrator creates such a connection by hand in the settings. It takes a WordPress user, an access level and an optional expiry in days. For pure content work, pick an Editor account instead of an administrator.

Tokens are stored only as hashes. You can rotate a connection's secret in one click or revoke the connection.

AlphaBridge keeps the latest 200 tool calls in an audit log. Each entry holds the time, the user, the tool and the result. It stores the names of the arguments, not their values. The settings page shows the newest entries. Older entries are overwritten, and the log can be switched off. So check that it is on.

Make a complete backup of files and database before you switch on write access. Keep it outside the site and check that you can restore it. Many hosts back up automatically, so check whether and how often yours does. Try larger changes on a staging copy first, where you have one. Where a tool offers a preview, look at it before you apply the change.

Pro creates an undo point when Claude edits a page or a file. Pro keeps the newest 50, each for 7 days by default, adjustable from 1 to 30 days. Pro's shop, SEO and user tools have no undo, and database writes have none either. Details are in the guide Undo AI changes with Pro.

Pro checks the syntax of PHP before it saves it, for files up to 512 KB. After each PHP edit to an active plugin, the active theme or a snippet, Pro calls the site. If the site no longer loads, Pro puts the old version back. The test calls the home page, not the checkout or cron jobs. Activating a plugin or theme runs without this test, and so does Site Deploy in Agency.

Know the limits, too. AlphaBridge checks whether a call is allowed. It does not check whether the call is correct or what you meant. AI assistants make mistakes. They can also follow instructions that someone hid in a comment, a page or a file. And changing an order status can send e-mails to your customers.

The whole security model is on the security page.

• Back up files and database completely, and keep the backup outside the site.
• Test once that the backup can be restored.
• Let the AI read and advise first, before you switch on write access.
• Give each connection the narrowest access level that does the job.
• For connections made by hand, use a WordPress account with only the rights the work needs.
• Set an expiry for one-off jobs, and revoke connections you no longer use.
• Switch on write access only for the work, and off again afterwards.
• After switching on, turn off unneeded tools under Fine-tuning.
• To block Pro's tools that write or delete theme and plugin files, set DISALLOW_FILE_EDIT in wp-config.php.
• Ask for a preview first where a tool offers one.
• Try updates, file and database changes on a staging copy first.
• Be careful when the AI works with content from strangers, such as comments.
• Read the audit log after the work.
• With Pro, keep the undo token from each answer until you have checked the result.