claudeus_wp_comments__trash
Move a comment to trash. Comment can be restored later or permanently deleted.
This record as markdown: /tools/deus-h-claudeus-wp-mcp/claudeus-wp-comments--trash.md
What claudeus_wp_comments__trash does on Claudeus WordPress MCP
AI agents call claudeus_wp_comments__trash to permanently remove resources in Claudeus WordPress MCP, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Why claudeus_wp_comments__trash is rated Critical
Trashing a comment is a reversible soft-delete (can be restored), which would normally be Write. However, the description explicitly notes it can lead to permanent deletion, and trash operations are conventionally classified as destructive. The reversibility lowers severity to medium, but the destructive pathway justifies the Destructive category over Write.
From the tool's definition Move a comment to trash. Comment can be restored later or permanently deleted.
Attacks that exploit this kind of access
The rule that runs claudeus_wp_comments__trash 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_comments__trash, this is the rule to start with:
claudeus_wp_comments__trash is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect Claudeus WordPress MCP, apply this rule, and every claudeus_wp_comments__trash call is checked against it from then on.
Questions about claudeus_wp_comments__trash
Move a comment to trash. Comment can be restored later or permanently deleted. It is categorised as a Destructive tool in the Claudeus WordPress MCP MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Claudeus WordPress MCP server in PolicyLayer and add a rule for claudeus_wp_comments__trash: 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_comments__trash is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the claudeus_wp_comments__trash 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_comments__trash. 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_comments__trash 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.
Across the catalogue