wordpress_update_theme_json · WordPress MCP Server MCP

WHAT IT DOES

What wordpress_update_theme_json does on WordPress MCP Server

AI agents use wordpress_update_theme_json 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_theme_json needs a policy

The tool updates (modifies) theme JSON configuration, which is a reversible write operation. While the description is empty, the name and server context strongly indicate theme file modification. Severity is high because misconfigured theme JSON could break site layout/functionality, but it's reversible via restore, so not Destructive.

From the tool's definition Tool name 'wordpress_update_theme_json' indicates modification of theme configuration file; context shows this server enables 'complete control over content, themes, plugins, files'; sibling tools like 'wordpress_activate_theme' and bulk operations suggest…

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

wordpress_update_theme_json Rate-limited

wordpress_update_theme_json 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_theme_json": {
      "limits": [
        {
          "counter": "wordpress_update_theme_json_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_theme_json

What does the wordpress_update_theme_json tool do? +

wordpress_update_theme_json. 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_theme_json? +

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

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

Can I rate-limit wordpress_update_theme_json? +

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

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

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