wordpress_set_seo_meta · WordPress MCP Server MCP

WHAT IT DOES

What wordpress_set_seo_meta does on WordPress MCP Server

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

Setting SEO metadata (meta tags, descriptions, keywords) creates or modifies content metadata reversibly. This is a Write operation—it doesn't execute code, delete data, or cause financial transactions. Severity is medium because misconfiguration could degrade site visibility or be used for malicious SEO manipulation, but changes are reversible.

From the tool's definition Tool name 'wordpress_set_seo_meta' indicates it sets/modifies SEO metadata. The sibling tools show this server has write, execute, and destructive capabilities (backup, delete, activate). The empty description limits certainty.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

wordpress_set_seo_meta Rate-limited

wordpress_set_seo_meta 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_set_seo_meta": {
      "limits": [
        {
          "counter": "wordpress_set_seo_meta_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_set_seo_meta

What does the wordpress_set_seo_meta tool do? +

wordpress_set_seo_meta. 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_set_seo_meta? +

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

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

Can I rate-limit wordpress_set_seo_meta? +

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

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

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