claudeus_wp_content__get_post_autosave

What claudeus_wp_content__get_post_autosave does on Claudeus WordPress MCP

AI agents call claudeus_wp_content__get_post_autosave to retrieve information from Claudeus WordPress MCP without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

Why claudeus_wp_content__get_post_autosave is rated Low

This tool only queries and retrieves WordPress autosave revisions, which are historical snapshots of post drafts. It performs no side effects, creates no new data, executes no code, and irreversibly deletes nothing. The operation is read-only and has minimal blast radius even if misused by an AI agent, as it merely exposes existing autosave records that WordPress already maintains internally.

From the tool's definition Tool name contains 'get' and description states 'Get a specific autosave of a post' — retrieves autosaved post data without modification.

The rule that runs claudeus_wp_content__get_post_autosave safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Claudeus WordPress MCP, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For claudeus_wp_content__get_post_autosave, this is the rule to start with:

{
  "version": "1",
  "default": "deny",
  "tools": {
    "claudeus_wp_content__get_post_autosave": {}
  }
}

Questions about claudeus_wp_content__get_post_autosave