publish_page · WordPress MCP Server MCP: Risk & Policy

WHAT IT DOES

What publish_page does on WordPress MCP Server

AI agents use publish_page to create or update resources in WordPress MCP Server — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your WordPress MCP Server environment.

WHY IT NEEDS A POLICY

Why publish_page needs a policy

This is a Write operation because it creates or modifies data reversibly — publishing a page changes its visibility and status but can be undone by unpublishing. The severity is high because publishing a page affects public-facing content and site integrity; a misused call could publish sensitive, incomplete, or incorrect content to a live WordPress site.

From the tool's definition The tool description states it will 'Publish a draft or pending page immediately' — this modifies the state of a page from draft/pending to published, making it live on the WordPress site.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

publish_page Rate-limited

publish_page stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "publish_page": {
      "limits": [
        {
          "counter": "publish_page_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches WordPress MCP Server, so you can run agents against it safely.

FAQ

Questions about publish_page

What does the publish_page tool do? +

Publish a draft or pending page immediately. It is categorised as a Write tool in the WordPress MCP Server MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on publish_page? +

Register the WordPress MCP Server MCP server in PolicyLayer and add a rule for publish_page: allow, deny, rate-limit, or require approval. Point your MCP client at the PolicyLayer proxy URL and the rule is enforced on every call, before it reaches WordPress MCP Server. Nothing to install.

What risk level is publish_page? +

publish_page is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit publish_page? +

Yes. Add a rate_limit block to the publish_page rule in your PolicyLayer policy. For example, setting max: 10 and window: 60 limits the tool to 10 calls per minute. Rate limits are tracked per agent session and reset automatically.

How do I block publish_page completely? +

Set action: deny in the PolicyLayer policy for publish_page. The AI agent will receive a policy violation error and cannot call the tool. You can also include a reason field to explain why the tool is blocked.

What MCP server provides publish_page? +

publish_page is provided by the WordPress MCP Server MCP server (wolffcatskyy/wordpress-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.