revision_get
Ruft den vollständigen Inhalt einer spezifischen Revision ab
This record as markdown: /tools/c-sakel-wp-mcp-server/revision-get.md
What revision_get does on WordPress MCP Server
AI agents call revision_get 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_get is rated Low
This tool retrieves/fetches historical revision data from WordPress. It performs a read-only query of existing content without modifying, deleting, or executing any operations. The action is passive data retrieval, fitting the Read category. Severity is low because accessing revision history does not expose sensitive operational risk, though information disclosure should still be considered in access control.
From the tool's definition Tool name 'revision_get' and description 'Ruft den vollständigen Inhalt einer spezifischen Revision ab' (retrieves the complete content of a specific revision) indicate a retrieval operation with no side effects.
Attacks that exploit this kind of access
The rule that runs revision_get 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_get, this is the rule to start with:
revision_get 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_get call is checked against it from then on.
Questions about revision_get
Ruft den vollständigen Inhalt einer spezifischen Revision ab. 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_get: 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_get 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_get 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_get. 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_get 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