wordpress_convert_to_webp · WordPress MCP Server MCP

WHAT IT DOES

What wordpress_convert_to_webp does on WordPress MCP Server

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

Converting images to WebP format modifies file content and storage, qualifying as a Write operation (creates or modifies data reversibly). Severity is medium because bulk media conversion could impact site performance or storage, but the operation is reversible by reconverting or restoring from backups.

From the tool's definition Tool name 'wordpress_convert_to_webp' indicates conversion/transformation of media files. No description provided to clarify intent, but conversion of media formats is a file modification operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

wordpress_convert_to_webp Rate-limited

wordpress_convert_to_webp 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_convert_to_webp": {
      "limits": [
        {
          "counter": "wordpress_convert_to_webp_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_convert_to_webp

What does the wordpress_convert_to_webp tool do? +

wordpress_convert_to_webp. 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_convert_to_webp? +

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

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

Can I rate-limit wordpress_convert_to_webp? +

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

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

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