wordpress_update_page · MCP Wordpress MCP: Risk & Policy

WHAT IT DOES

What wordpress_update_page does on MCP Wordpress

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

This tool modifies existing WordPress pages, which is a Write operation. It's classified as high severity because unauthorized page updates could deface a website, inject malicious content, or alter critical information, affecting all visitors. The confidence is high despite empty description because the tool name and server context clearly indicate WordPress page modification capabilities.

From the tool's definition Tool name 'wordpress_update_page' indicates modification of page data. Sibling tools include destructive operations (wordpress_delete_page, wordpress_delete_post) and creation operations (wordpress_create_page, wordpress_create_post), confirming this server…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

wordpress_update_page Rate-limited

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

FAQ

Questions about wordpress_update_page

What does the wordpress_update_page tool do? +

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

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

What risk level is wordpress_update_page? +

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

Can I rate-limit wordpress_update_page? +

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

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

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