wordpress_copy_file · WordPress MCP Server MCP

WHAT IT DOES

What wordpress_copy_file does on WordPress MCP Server

AI agents use wordpress_copy_file 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_copy_file needs a policy

File copying creates new data and modifies the filesystem state, classifying it as Write rather than Read. The severity is medium because file copying on a WordPress server can have moderate impact (duplicate large files, consume disk space, or copy sensitive files to unintended locations), but it is reversible through deletion.

From the tool's definition Tool name 'wordpress_copy_file' indicates file copying/duplication operations within WordPress.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

wordpress_copy_file Rate-limited

wordpress_copy_file 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_copy_file": {
      "limits": [
        {
          "counter": "wordpress_copy_file_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_copy_file

What does the wordpress_copy_file tool do? +

wordpress_copy_file. 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_copy_file? +

Register the WordPress MCP Server MCP server in PolicyLayer and add a rule for wordpress_copy_file: 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_copy_file? +

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

Can I rate-limit wordpress_copy_file? +

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

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

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