revision_list
Listet alle Revisionen eines Posts/einer Seite auf
This record as markdown: /tools/c-sakel-wp-mcp-server/revision-list.md
What revision_list does on WordPress MCP Server
AI agents call revision_list to retrieve information from WordPress MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.
Why revision_list is rated Low
The tool performs a query/retrieval operation to list revisions. It has no side effects, does not execute code, does not modify data, and does not delete or move money. This fits squarely into the Read category with low severity since viewing revision history poses minimal risk even if an AI agent accesses it unexpectedly.
From the tool's definition Tool name is 'revision_list' and description states 'Listet alle Revisionen eines Posts/einer Seite auf' (Lists all revisions of a post/page).
Attacks that exploit this kind of access
The rule that runs revision_list 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 revision_list, this is the rule to start with:
revision_list is read-only, so it stays allowed. 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 revision_list call is checked against it from then on.
Questions about revision_list
Listet alle Revisionen eines Posts/einer Seite auf. It is categorised as a Read tool in the WordPress MCP Server MCP Server, which means it retrieves data without modifying state.
Register the WordPress MCP Server MCP server in PolicyLayer and add a rule for revision_list: 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.
revision_list is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the revision_list 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 revision_list. 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.
revision_list 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