wordpress_moderate_comment · MCP Wordpress MCP

WHAT IT DOES

What wordpress_moderate_comment does on MCP Wordpress

AI agents use wordpress_moderate_comment to create or update resources in MCP Wordpress — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your MCP Wordpress environment.

WHY IT NEEDS A POLICY

Why wordpress_moderate_comment needs a policy

This tool modifies a comment's status (e.g., approve, hold, spam) which is a data modification operation. While it alters state, it is reversible—a moderated comment can be un-moderated. This places it in Write rather than Destructive. Severity is medium because improper moderation could suppress legitimate user content or approve spam, affecting site quality and user experience, but the effects are reversible.

From the tool's definition Tool description states it changes comment status, which modifies data. The word 'moderate' and 'changing status' indicates reversible modification rather than deletion.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

wordpress_moderate_comment Rate-limited

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

View as policy code

policy.json

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

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches MCP Wordpress, so you can run agents against it safely.

FAQ

Questions about wordpress_moderate_comment

What does the wordpress_moderate_comment tool do? +

Moderate a WordPress comment by changing its status. It is categorised as a Write tool in the MCP Wordpress MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on wordpress_moderate_comment? +

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

What risk level is wordpress_moderate_comment? +

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

Can I rate-limit wordpress_moderate_comment? +

Yes. Add a rate_limit block to the wordpress_moderate_comment 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 wordpress_moderate_comment completely? +

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

wordpress_moderate_comment is provided by the MCP Wordpress MCP server (crunchtools/mcp-wordpress). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.