claudeus_wp_content__create_block_autosave
Create an autosave for a reusable block
This record as markdown: /tools/deus-h-claudeus-wp-mcp/claudeus-wp-content--create-block-autosave.md
What claudeus_wp_content__create_block_autosave does on Claudeus WordPress MCP
AI agents use claudeus_wp_content__create_block_autosave to create or update resources in Claudeus WordPress MCP, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your Claudeus WordPress MCP environment.
Why claudeus_wp_content__create_block_autosave is rated Medium
This tool creates (writes) autosave data for WordPress reusable blocks. Autosaves are reversible — they can be discarded or replaced — so this is Write rather than Destructive. The blast radius is medium because a malicious agent could flood the database with autosaves or corrupt editor state, but the operation is not irreversible and does not involve deletion, financial transactions, or arbitrary code execution.
From the tool's definition Tool name includes 'create' and description states 'Create an autosave for a reusable block' — both indicating a write operation that modifies state by storing a new autosave record.
Attacks that exploit this kind of access
The rule that runs claudeus_wp_content__create_block_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__create_block_autosave, this is the rule to start with:
claudeus_wp_content__create_block_autosave 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 Claudeus WordPress MCP, apply this rule, and every claudeus_wp_content__create_block_autosave call is checked against it from then on.
Questions about claudeus_wp_content__create_block_autosave
Create an autosave for a reusable block. It is categorised as a Write tool in the Claudeus WordPress MCP MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the Claudeus WordPress MCP server in PolicyLayer and add a rule for claudeus_wp_content__create_block_autosave: 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 Claudeus WordPress MCP. Nothing to install.
claudeus_wp_content__create_block_autosave 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 claudeus_wp_content__create_block_autosave 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 claudeus_wp_content__create_block_autosave. 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.
claudeus_wp_content__create_block_autosave is provided by the Claudeus WordPress MCP server (deus-h/claudeus-wp-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on Claudeus WordPress, and thousands of servers like it.
This server
Across the catalogue