wordpress_update_widget · WordPress MCP Server MCP

WHAT IT DOES

What wordpress_update_widget does on WordPress MCP Server

AI agents use wordpress_update_widget 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_update_widget needs a policy

The tool performs a write operation that creates or modifies widget settings reversibly. While the description is empty (lowering confidence slightly), the name clearly indicates an update/modification action. This falls under Write rather than Execute because it modifies configuration data rather than running arbitrary code.

From the tool's definition Tool name 'wordpress_update_widget' indicates modification of widget data/configuration on a WordPress site.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

wordpress_update_widget Rate-limited

wordpress_update_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": {
    "wordpress_update_widget": {
      "limits": [
        {
          "counter": "wordpress_update_widget_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_update_widget

What does the wordpress_update_widget tool do? +

wordpress_update_widget. 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_update_widget? +

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

What risk level is wordpress_update_widget? +

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

Can I rate-limit wordpress_update_widget? +

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

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

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