update_wordpress_post · WordPress AI Content System MCP

WHAT IT DOES

What update_wordpress_post does on WordPress AI Content System

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

WHY IT NEEDS A POLICY

Why update_wordpress_post needs a policy

This tool modifies existing WordPress posts, which is a reversible write operation. It does not delete data (which would be Destructive) nor execute arbitrary code (which would be Execute). However, the severity is high because an AI agent misusing this tool could modify published content at scale, affecting site reputation, SEO, or user trust.

From the tool's definition Tool name 'update_wordpress_post' and description 'Update an existing WordPress post by ID' indicate modification of existing data. The verb 'update' is explicitly a Write operation that modifies post content reversibly.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_wordpress_post Rate-limited

update_wordpress_post 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": {
    "update_wordpress_post": {
      "limits": [
        {
          "counter": "update_wordpress_post_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 AI Content System, so you can run agents against it safely.

FAQ

Questions about update_wordpress_post

What does the update_wordpress_post tool do? +

Update an existing WordPress post by ID. It is categorised as a Write tool in the WordPress AI Content System MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on update_wordpress_post? +

Register the WordPress AI Content System MCP server in PolicyLayer and add a rule for update_wordpress_post: 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 AI Content System. Nothing to install.

What risk level is update_wordpress_post? +

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

Can I rate-limit update_wordpress_post? +

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

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

update_wordpress_post is provided by the WordPress AI Content System MCP server (ssolis-ti/wordpress_content_ai_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.