mcp_move_widget

Move a widget to a different sidebar

SERVERWordpress SOURCE@cavort-it-systems/wordpress-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-cvrt-jh-wordpress-mcp/mcp-move-widget.md

WHAT IT DOES

What mcp_move_widget does on Wordpress

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

RISK

Why mcp_move_widget is rated Medium

Moving a widget changes the configuration/structure of a WordPress site by altering where UI components appear. This is a reversible modification (Write) rather than destructive deletion. Severity is medium because misuse could deface the site's layout and impair functionality, but the change is non-destructive and can be undone by moving the widget back.

From the tool's definition Tool name 'mcp_move_widget' and description 'Move a widget to a different sidebar' indicate modification of widget placement/configuration.

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs mcp_move_widget safely

PolicyLayer is an MCP gateway: it sits between your AI agents and Wordpress, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For mcp_move_widget, this is the rule to start with:

mcp_move_widget Rate-limited

mcp_move_widget 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": {
    "mcp_move_widget": {
      "limits": [
        {
          "counter": "mcp_move_widget_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect Wordpress, apply this rule, and every mcp_move_widget call is checked against it from then on.

FAQ

Questions about mcp_move_widget

What does the mcp_move_widget tool do? +

Move a widget to a different sidebar. It is categorised as a Write tool in the 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 mcp_move_widget? +

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

What risk level is mcp_move_widget? +

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

Can I rate-limit mcp_move_widget? +

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

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

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

KEEP EXPLORING

More on Wordpress, and thousands of servers like it.

This server

All 314 Wordpress tools →

Across the catalogue

move-task on Kanban MCP Server → The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →