What can an AI agent do on your site?
An MCP connection lets a client request operations from WordPress. The authenticated user, enabled tools and each operation’s permission checks determine the available access. Your prompt describes the job; it is not a substitute for those controls.
- Authentication
- Establishes which WordPress user the client acts as.
- Capabilities
- Determine whether that user can perform the requested operation.
- Tool settings
- Control the tools EMCP exposes on this site.
- Operation gates
- Some sensitive actions require additional confirmation parameters.
- Your review
- Checks whether an authorized change is also the change you intended.
A tool’s confirmation parameter does not itself prove that a person reviewed the change. Set your client’s approval preferences and ask to see the target and proposed edit before a consequential action. Keep your normal WordPress hardening and backup practices in place.
OAuth or an Application Password?
Both methods authenticate a client. Choose based on your client’s support and the identity you want it to use. For remote connections, use HTTPS and copy the complete server URL from EMCP Tools → Connection.
Scroll the table horizontally on smaller screens.
| What to check | EMCP OAuth | Application Password |
|---|---|---|
| Connection | Approve a browser sign-in from a supported client. | Provide a separate WordPress API credential in the client’s connection settings. |
| Acting identity | The approving user. By default, approval requires administrator-level access. | The user who owns the credential, subject to the tool’s required capabilities. |
| Best fit | A supported client and a deliberate administrator connection. | A credential-based client, or a dedicated user whose task permissions you have checked. |
| Revoke access | EMCP Tools → Connection → Connected apps. | The user’s WordPress profile → Application Passwords. |
OAuth avoids copying a password into your configuration, but an administrator token still acts as an administrator. With an Application Password, use a dedicated user with the permissions the task requires. Verify the specific tool before relying on a role such as Editor; site administration and page editing need different capabilities.
Create a separately named credential per connection, store it securely, and keep it out of chat prompts, screenshots and repositories. Base64 encoding is not encryption. See WordPress’s Application Password guidance for credential management.
Enable the tools the job needs.
Open EMCP Tools → Tools, review the available tools, and save your selection. Sensitive writes are opt-in; this is not a blanket promise that every operation capable of changing a page is disabled. Check the tools involved in your task.
These settings apply across clients. Turning a tool off affects other clients connecting to the same site. A missing tool can also reflect an inactive integration or a tier requirement, so inspect its dependency information before changing permissions.
Compact mode exposes three dispatcher tools for discovery and execution. It keeps the advertised list smaller; it does not bypass disabled tools or capability checks. Follow the tool-control guide for the current interface.
Verify the site before changing it.
Check the configured domain and selected WordPress account. Then request a small read-only result, especially when your client connects to several sites. Read-only results can still contain private information, so limit the request to what you need.
On the WordPress site I selected, list up to five pages I can access. Return their titles, IDs and publication status. Do not create, update or delete anything. If a required tool is unavailable, explain what is missing.
Confirm that the response contains real records from the intended site. An agent describing what it would do is not evidence of a working connection. Check the request log and client result. If discovery fails, use the no-tools guide or authentication troubleshooting instead of enabling every tool.
Start with a draft on staging.
Choose a staging page and check its ID and draft status. Ask for one small change, such as revising a heading. Specify that it must remain a draft, and inspect the tool’s inputs before authorizing the edit. Do not assume a universal publishing default.
- 01
Confirm the target
Site, page ID, current status and the exact edit.
- 02
Read the change back
Retrieve the saved content and confirm it matches the request.
- 03
Preview the result
Check desktop and mobile. Decide separately whether to publish.
For Elementor work, inspect the editable structure as well as the frontend. Keep a suitable backup or revision before larger changes. Recovery differs by operation: a page revision cannot undo a refund, restore every deleted file or reverse an external side effect. The first-page walkthrough and change-history documentation explain the relevant workflows.
Know how to stop access.
The MCP Log keeps the latest 100 requests, including the tool or method, result status and duration. Use it to connect a client error with a server-side outcome. It is a recent-request buffer, not a permanent audit record or a complete before-and-after history.
Revoke the connected app.
Open EMCP Tools → Connection → Connected apps. Check the client and connected user, then choose Revoke for the intended app.
Revoke the credential.
Open the owning user’s WordPress profile. Under Application Passwords, locate the named credential and revoke it.
After revoking, check that the old connection cannot make a new authenticated request without signing in again or receiving a new credential. If the client has another connection or credential, review that separately. Removing access does not undo saved edits or recall data already returned to the client.
Self-hosted tools. A connected AI client.
EMCP runs tools inside WordPress. The results return to your selected client and may be processed by its model provider. Hosting WordPress yourself does not mean that all AI processing stays on your server.
With a direct connection, the client exchanges requests and results with your site. If you choose the hosted gateway, they also pass through EMCP Cloud. Review your provider’s data settings and the services you enable before requesting customer records, private content or other sensitive information.
See the WordPress MCP architecture, hosted gateway guide and EMCP privacy policy for the route you use.
WordPress MCP security FAQ
Does connecting an AI agent give it administrator access?
It depends on the identity used. With EMCP’s default OAuth setup, an administrator approves the connection and the token acts as that user. An Application Password authenticates as the WordPress user who owns it. Each tool has its own permission checks; authentication does not make an administrator account read-only.
Is a WordPress Application Password read-only?
No. It is a separate, revocable API credential tied to a WordPress user. The user’s capabilities and the requested endpoint determine what it can do. A descriptive credential name does not restrict its permissions.
Can I connect a dedicated user with fewer permissions?
An Application Password can identify a dedicated WordPress user. Choose permissions for the actual task and verify the required tool with that account. An Editor role is not sufficient for every EMCP operation. The standard OAuth approval flow requires administrator-level access.
Are tool settings different for each AI client?
EMCP’s Tools settings apply across clients connecting to that site. They are not separate permission profiles for Claude, Cursor or another client. Each request is also subject to the connected user’s capabilities.
Does Compact mode bypass disabled tools?
No. Compact mode changes how tools are discovered and called, using three dispatcher tools. Disabled tools and capability checks still apply. A smaller advertised tool list is not a different permission model.
Does revoking access undo previous changes?
No. Revocation removes the relevant credential or token access. Saved edits remain, and previously returned data may still exist in the client. Review revisions, supported change history or backups separately when recovering a change.
Does self-hosting keep tool results away from the AI provider?
No. EMCP executes tools on your WordPress installation, but results return to the selected client and may be processed by its model provider. If you choose the hosted EMCP Cloud gateway, requests and results also pass through that service.
Sources & review notes
Published by the EMCP team. Reviewed on 22 September 2026 against the product documentation and implementation of OAuth, tool controls and request logging. Examples and diagrams explain a workflow; they are not a security certification or a recorded live-site test.
- EMCP: OAuth, tool settings, Compact mode and hosted gateway.
- WordPress: Application Passwords and REST API credential management.