wp_update_post_content · Mcp Wordpress MCP: Risk & Policy

WHAT IT DOES

What wp_update_post_content does on Mcp Wordpress

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

WHY IT NEEDS A POLICY

Why wp_update_post_content needs a policy

This tool modifies post content reversibly (updates can be undone by subsequent updates or version control), so it falls under Write rather than Destructive. However, severity is high because overwriting post content could impact site visibility, SEO, user-facing information, and site traffic. An AI agent with unsupervised access could corrupt or replace critical website content.

From the tool's definition Tool name 'wp_update_post_content' and description 'Replace the entire raw content of a WordPress post' indicate modification of existing post data via the WordPress REST API.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

wp_update_post_content Rate-limited

wp_update_post_content 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": {
    "wp_update_post_content": {
      "limits": [
        {
          "counter": "wp_update_post_content_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 Mcp Wordpress, so you can run agents against it safely.

FAQ

Questions about wp_update_post_content

What does the wp_update_post_content tool do? +

Replace the entire raw content of a WordPress post. It is categorised as a Write tool in the Mcp Wordpress MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on wp_update_post_content? +

Register the Mcp Wordpress MCP server in PolicyLayer and add a rule for wp_update_post_content: 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 Mcp Wordpress. Nothing to install.

What risk level is wp_update_post_content? +

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

Can I rate-limit wp_update_post_content? +

Yes. Add a rate_limit block to the wp_update_post_content 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 wp_update_post_content completely? +

Set action: deny in the PolicyLayer policy for wp_update_post_content. 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 wp_update_post_content? +

wp_update_post_content is provided by the Mcp Wordpress MCP server (leonardobora/mcp-wordpress). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.