wordpress_update_page · ItchWP MCP: Risk & Policy

WHAT IT DOES

What wordpress_update_page does on ItchWPMCP

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

WHY IT NEEDS A POLICY

Why wordpress_update_page needs a policy

The tool modifies page properties and content reversibly. An AI agent with access could change page content, publish unpublished pages, or alter navigation structure, affecting site visibility and user experience. This is Write rather than Execute because it updates specific fields rather than running arbitrary code, and is not Destructive since updates can be reverted.

From the tool's definition Tool description explicitly states 'Update a WordPress page' — a reversible modification operation. The parameters listed (title, content, excerpt, slug, status, parent, menu order) are all content/metadata updates, not deletions.

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 ItchWPMCP, so you can run agents against it safely.

FAQ

Questions about wordpress_update_page

What does the wordpress_update_page tool do? +

Update a WordPress page by ID. Only title, content, excerpt, slug, status, parent, and menu order are supported. It is categorised as a Write tool in the ItchWPMCP 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 ItchWP 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 ItchWPMCP. 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 ItchWP MCP server (manofsadness/itchwpmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.