wordpress_create_comment
AI agents use wordpress_create_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.
The tool creates new comments on a WordPress site, which modifies data reversibly. This is a Write operation rather than Read (which would only retrieve data), Execute (which would run arbitrary code), or Destructive (comments can be deleted/modified later).
From the tool's definition Tool name 'wordpress_create_comment' indicates creation of comment data. Sibling tools include destructive operations (wordpress_delete_comment, wordpress_delete_post, wordpress_delete_page, wordpress_delete_media), confirming this server manipulates…
Attacks that exploit this kind of access
wordpress_create_comment. 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.
Register the MCP Wordpress MCP server in PolicyLayer and add a rule for wordpress_create_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.
wordpress_create_comment 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 wordpress_create_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.
Set action: deny in the PolicyLayer policy for wordpress_create_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.
wordpress_create_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.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →