AI agents use wordpress_move_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.
Moving files is a reversible write operation that reorganizes or relocates data within the WordPress file system. While reversible (files can be moved back), this has high severity due to potential to disrupt site structure, break plugin/theme functionality, or expose sensitive files. Not Destructive because files are not deleted.
From the tool's definition Tool name 'wordpress_move_file' indicates file system manipulation. The server description explicitly mentions 'file system operations' as a capability. Despite the empty tool description, the name and context indicate this modifies file locations.
Documented attack patterns abuse exactly the kind of access wordpress_move_file gives an agent:
PolicyLayer is an MCP gateway — it sits between your AI agents and WordPress MCP Server, and nothing reaches the server without passing your rules. This is the rule we recommend for wordpress_move_file:
{
"version": "1",
"default": "deny",
"tools": {
"wordpress_move_file": {
"limits": [
{
"counter": "wordpress_move_file_rate",
"window": "minute",
"max": 30,
"scope": "grant"
}
]
}
}
}wordpress_move_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.
Free to start. No card required.
wordpress_move_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.
Register the WordPress MCP Server MCP server in PolicyLayer and add a rule for wordpress_move_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.
wordpress_move_file 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_move_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.
Set action: deny in the PolicyLayer policy for wordpress_move_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.
wordpress_move_file is provided by the WordPress MCP Server MCP server (raheesahmed/wordpress-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Deterministic rules across all 190 WordPress MCP Server tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.
Free to start. No card required.
190 WordPress MCP Server tools catalogued and risk-classified — across an index of 42,500+ MCP servers.