wordpress_update_post · WordPress MCP Server MCP

WHAT IT DOES

What wordpress_update_post does on WordPress MCP Server

AI agents use wordpress_update_post 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 wordpress_update_post needs a policy

The tool updates (modifies) post content reversibly. While high-severity due to potential for widespread content damage across a live WordPress site if misused by an agent, it remains in Write rather than Destructive since updates are reversible. The empty description lowers confidence slightly, but the tool name is explicit enough to classify with reasonable certainty.

From the tool's definition Tool name 'wordpress_update_post' indicates modification of existing post data. No description provided, but the name clearly implies a write operation on WordPress posts.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

wordpress_update_post Rate-limited

wordpress_update_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": {
    "wordpress_update_post": {
      "limits": [
        {
          "counter": "wordpress_update_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 MCP Server, so you can run agents against it safely.

FAQ

Questions about wordpress_update_post

What does the wordpress_update_post tool do? +

wordpress_update_post. 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 wordpress_update_post? +

Register the WordPress MCP Server MCP server in PolicyLayer and add a rule for wordpress_update_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 MCP Server. Nothing to install.

What risk level is wordpress_update_post? +

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

Can I rate-limit wordpress_update_post? +

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

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

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