wordpress_duplicate_post · WordPress MCP Server MCP

WHAT IT DOES

What wordpress_duplicate_post does on WordPress MCP Server

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

WHY IT NEEDS A POLICY

Why wordpress_duplicate_post needs a policy

Duplicating a post creates new data (reversible through deletion), making this a Write operation. It does not delete data (not Destructive), execute arbitrary code (not Execute), involve financial transactions (not Financial), or trigger read-only behavior (not Read). Severity is medium because uncontrolled duplication could spam the site or create unwanted content, but the action is reversible.

From the tool's definition Tool name 'wordpress_duplicate_post' indicates creating a copy of an existing post. The description is empty, limiting direct confirmation, but the naming pattern aligns with WordPress operations that modify content by creating new resources.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

wordpress_duplicate_post Rate-limited

wordpress_duplicate_post 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_duplicate_post": {
      "limits": [
        {
          "counter": "wordpress_duplicate_post_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 WordPress MCP Server, so you can run agents against it safely.

FAQ

Questions about wordpress_duplicate_post

What does the wordpress_duplicate_post tool do? +

wordpress_duplicate_post. It is categorised as a Write tool in the WordPress MCP Server 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_duplicate_post? +

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

What risk level is wordpress_duplicate_post? +

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

Can I rate-limit wordpress_duplicate_post? +

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

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

wordpress_duplicate_post is provided by the WordPress MCP Server MCP server (tonypepperwidow123-blip/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.