PageForge 1.3: check every run before it writes, update generated pages, spintax and resumable batches. See what changed
Account Get it free

Every MCP request is checked for a valid credential, the right scope, the WordPress user's permissions and rate limits. Free can only grant read and preview.

Since 1.2.0 Updated November 18, 20263 min read

PageForge checks every MCP request in layers, and each layer runs on every call:

  1. Credential. The request carries a valid OAuth token or personal access token in a header.
  2. Audience. An OAuth token must have been issued for this site’s MCP endpoint. A token minted for another server is refused.
  3. Scope. The tool being called must be covered by the scopes the connection was granted.
  4. WordPress permissions. The tool runs as the WordPress user who approved the connection, and that user’s own capabilities are checked.
  5. Tool checks. Each tool validates its own input and checks access to each post it touches.

Scopes

Permission shown on screenScopeWhat it allowsEdition
Read PageForge datapageforge:readView templates, generated pages, SEO status and diagnosticsFree and Pro
Preview and validatepageforge:previewRun previews and validation without changing anythingFree and Pro
Create and update contentpageforge:writeCreate, update and publish generated pagesPro
Operate campaignspageforge:campaignsStart, pause, resume, retry and cancel campaignsPro
Manage SEOpageforge:seoUpdate meta titles, descriptions, schema and internal linksPro
Manage data sourcespageforge:contentManage datasets, CSV imports and Google Sheets connectionsPro
Read analyticspageforge:analyticsRead analytics data for generated pagesPro
Administer PageForgepageforge:adminChange settings and connector configurationPro, never granted by default

Free can only ever grant the first two. Pro scopes also need an active license, checked on every call, so a lapsed license stops write access at once. Broader scopes include the narrower read and preview scopes they depend on, but Administer PageForge never includes content changes, and content scopes never include administration.

When a call lacks a scope, PageForge answers with a precise challenge so the client can ask for exactly what it needs:

HTTP/1.1 403 Forbidden
WWW-Authenticate: Bearer error="insufficient_scope", scope="pageforge:seo", ...

Who can connect

By default only administrators (users who can manage options) can approve an AI client or create a token. If that account later loses the right, its tokens stop working immediately. A personal access token can never hold more than its owner could do: write scopes need the right to edit posts, and the administration scope needs administrator rights. In Pro, publishing through MCP also requires the right to publish that post type.

Other protections

  • Rate limiting. Failed sign-in attempts are limited per IP address, and tools are metered by cost: reads are allowed more often than previews and changes. A client that hits a limit gets a 429 response with a Retry-After header.
  • Origin validation. Requests sent by a browser must come from your own site, chatgpt.com, chat.openai.com or claude.ai. Other origins are refused, which blocks DNS rebinding attacks. Server-to-server requests without an Origin header are allowed.
  • No caching. Authenticated responses are sent with Cache-Control: no-store, so proxies and browsers do not keep copies.
  • Hashed secrets. Personal access tokens and OAuth client secrets are stored as keyed hashes.
  • Short-lived tokens. OAuth access tokens expire quickly, and refresh tokens rotate on each use.
  • Headers only. Tokens are read from headers, never from URLs.

Revoke access

To stopDo this on PageForge > Connections
One OAuth connectionDisconnect under OAuth grants
One tokenRevoke under Personal access tokens
A suspected leaked tokenRotate it, then update the client
Every connector using a custom OAuth clientRevoke under OAuth clients
EverythingUntick the enable checkbox under MCP / AI Clients

Tip Create one token per client and per machine, so you can revoke one without touching the others.

Next: Let assistants make changes and Cursor, VS Code, Claude Code and other clients.

Was this page helpful?

↑↓ to move↵ to open