updateYoastSeo · WordPress MCP Server MCP: Risk & Policy

WHAT IT DOES

What updateYoastSeo does on WordPress MCP Server

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

This tool modifies post metadata reversibly without deleting data or executing arbitrary code. It falls into the Write category as it updates SEO-related metadata fields. Severity is medium because while the changes are reversible, SEO metadata manipulation could affect website visibility and search rankings, and an AI agent with uncontrolled use could degrade site SEO performance across multiple posts.

From the tool's definition Tool updates Yoast SEO metadata fields (focuskw, metadesc, title) on WordPress posts. The description indicates modification of post metadata through 'sets' (설정합니다). Sibling tools include createPost, updatePost patterns typical of WordPress CRUD operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

updateYoastSeo Rate-limited

updateYoastSeo 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": {
    "updateYoastSeo": {
      "limits": [
        {
          "counter": "updateyoastseo_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 updateYoastSeo

What does the updateYoastSeo tool do? +

WordPress 게시글의 Yoast SEO 메타데이터를 설정합니다. (focuskw, metadesc, title). 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 updateYoastSeo? +

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

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

Can I rate-limit updateYoastSeo? +

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

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

updateYoastSeo is provided by the WordPress MCP Server MCP server (ssong-openmaru-io/ai-mcp-wordpress). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.