update_media · WordPress MCP Server MCP: Risk & Policy

WHAT IT DOES

What update_media does on WordPress MCP Server

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

This tool modifies media file metadata in WordPress, which is a write operation. It does not delete data (which would be Destructive), does not execute arbitrary code (Execute), and does not involve financial transactions (Financial).

From the tool's definition Tool name 'update_media' and description 'Update the metadata of a media file' indicate modification of existing data. The action is reversible—metadata can be changed again or restored.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

update_media Rate-limited

update_media 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": {
    "update_media": {
      "limits": [
        {
          "counter": "update_media_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 update_media

What does the update_media tool do? +

Update the metadata of a media file in WordPress site. 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 update_media? +

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

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

Can I rate-limit update_media? +

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

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

update_media is provided by the WordPress MCP Server MCP server (obot-platform/wordpress-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.