wordpress_update_template_part · ItchWP MCP: Risk & Policy

WHAT IT DOES

What wordpress_update_template_part does on ItchWPMCP

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

WHY IT NEEDS A POLICY

Why wordpress_update_template_part needs a policy

The tool creates or modifies template data reversibly through the WordPress REST API. While 'update' operations are Write-category actions, the severity is elevated to 'high' because template parts control site-wide UI/functionality rendering; a malicious update could inject malicious code, deface the site, or redirect users, affecting all visitors.

From the tool's definition Tool name contains 'update' and description states 'Update an FSE template part' — this modifies existing template content in WordPress.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

wordpress_update_template_part Rate-limited

wordpress_update_template_part 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_template_part": {
      "limits": [
        {
          "counter": "wordpress_update_template_part_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 ItchWPMCP, so you can run agents against it safely.

FAQ

Questions about wordpress_update_template_part

What does the wordpress_update_template_part tool do? +

Update an FSE template part\. It is categorised as a Write tool in the ItchWPMCP 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_template_part? +

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

What risk level is wordpress_update_template_part? +

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

Can I rate-limit wordpress_update_template_part? +

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

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

wordpress_update_template_part is provided by the ItchWP MCP server (manofsadness/itchwpmcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.