wp_update_page
Aktualisiert eine bestehende WordPress-Seite
This record as markdown: /tools/c-sakel-wp-mcp-server/wp-update-page.md
What wp_update_page does on WordPress MCP Server
AI agents use wp_update_page 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 wp_update_page is rated Medium
This tool modifies existing WordPress pages, which is a reversible write operation. Severity is high because unauthorized updates could alter published content, damage site integrity, or inject malicious content into pages visible to users. The scope is limited to page updates (not deletion or financial operations), placing it in Write category rather than Destructive or Financial.
From the tool's definition Tool name 'wp_update_page' and description 'Aktualisiert eine bestehende WordPress-Seite' (Updates an existing WordPress page) indicate modification of existing content.
Attacks that exploit this kind of access
The rule that runs wp_update_page safely
PolicyLayer is an MCP gateway: it sits between your AI agents and WordPress MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For wp_update_page, this is the rule to start with:
wp_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.
The button opens the PolicyLayer dashboard: create your workspace, connect WordPress MCP Server, apply this rule, and every wp_update_page call is checked against it from then on.
Questions about wp_update_page
Aktualisiert eine bestehende WordPress-Seite. 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.
Register the WordPress MCP Server MCP server in PolicyLayer and add a rule for wp_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 WordPress MCP Server. Nothing to install.
wp_update_page is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the wp_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.
Set action: deny in the PolicyLayer policy for wp_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.
wp_update_page is provided by the WordPress MCP Server MCP server (c-sakel/wp-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on WordPress MCP Server, and thousands of servers like it.
This server
Across the catalogue