wp_set_comment_status

THE RISK

Medium Risk

Why wp_set_comment_status needs a policy

This tool modifies the state of a post attribute (comment enabled/disabled status) reversibly. It is not destructive (comments are not deleted, just disabled), not financial, and not executing arbitrary code. It fits Write category as it updates post configuration.

From the tool's definition Tool name 'wp_set_comment_status' and description 'Enable or disable comments on the post' indicate modification of post settings/metadata without deletion or irreversible data loss.

Documented attack patterns abuse exactly the kind of access wp_set_comment_status gives an agent:

POLICY

How to control wp_set_comment_status

PolicyLayer is an MCP gateway — it sits between your AI agents and Claudaborative Editing, and nothing reaches the server without passing your rules. This is the rule we recommend for wp_set_comment_status:

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "wp_set_comment_status": {
      "limits": [
        {
          "counter": "wp_set_comment_status_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

wp_set_comment_status 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.

Create a free account and register Claudaborative Editing — nothing to install.
Add this policy — paste it, or build it visually.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

LIMIT THIS TOOL →

Free to start. No card required.

EXPLORE

Related tools and policies

More Claudaborative Editing tools

Destructive wp_remove_blocks Remove one or more blocks from the post Destructive wp_remove_inner_blocks Remove inner blocks from a parent block Destructive wp_resolve_note Resolve (delete) a note and remove its association from the linked block. Write wp_add_note Add a note (block comment) to a specific block. Notes are editorial feedback visible in th Write wp_connect Connect to a WordPress site for collaborative editing. Not needed if the server was starte Write wp_create_post Create a new WordPress post and open it for editing Write wp_edit_block_text Make surgical find-and-replace text edits within a block. Write wp_insert_block Insert a new block at a position in the post. Supports nested blocks via innerBlocks.

All 32 Claudaborative Editing tools →

Write tools on other servers

M-Team MCP Server download_torrent YouTube MCP Server generate_video_title Android Forensics ADB MCP Server combine_reports 0xarchive web3_signup

Go deeper

The MCP Attack Database → Documented attack patterns against MCP deployments — and the policies that stop them.
Argument validation → Checking tool call arguments against schema and policy before they run.
Scoped token → Per-person credentials that grant a defined subset of servers and tools.
Rate Limiting MCP Tool Calls: A Practical Guide →
MCP Security: Why Prompt Guardrails Aren't Enough →

FAQ

Questions about wp_set_comment_status

What does the wp_set_comment_status tool do? +

Enable or disable comments on the post. It is categorised as a Write tool in the Claudaborative Editing MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on wp_set_comment_status? +

Register the Claudaborative Editing MCP server in PolicyLayer and add a rule for wp_set_comment_status: 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 Claudaborative Editing. Nothing to install.

What risk level is wp_set_comment_status? +

wp_set_comment_status is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit wp_set_comment_status? +

Yes. Add a rate_limit block to the wp_set_comment_status 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.

How do I block wp_set_comment_status completely? +

Set action: deny in the PolicyLayer policy for wp_set_comment_status. 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.

What MCP server provides wp_set_comment_status? +

wp_set_comment_status is provided by the Claudaborative Editing MCP server (pento/claudaborative-editing). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

Enforce policy on every Claudaborative Editing tool call.

Start from Claudaborative Editing, add the rest of your stack, and see everything your agents can call. Then put policy on all of it.

CHECK YOUR STACK →