generate_blog_post · WordPress AI Content System MCP

WHAT IT DOES

What generate_blog_post does on WordPress AI Content System

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

WHY IT NEEDS A POLICY

Why generate_blog_post needs a policy

This tool creates new content (blog post in Markdown format) which is reversible — posts can be edited, archived, or deleted afterward. It does not execute arbitrary code, delete data, or commit financial transactions. While it generates content that may be published via sibling tools like publish_to_wordpress, the generate_blog_post tool itself only produces output; it does not publish or apply modifications.

From the tool's definition Tool description states 'Generate a full SEO-optimized blog post in Markdown from a topic and keywords' — the word 'Generate' combined with 'blog post' indicates creation of new content.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

generate_blog_post Rate-limited

generate_blog_post 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": {
    "generate_blog_post": {
      "limits": [
        {
          "counter": "generate_blog_post_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 AI Content System, so you can run agents against it safely.

FAQ

Questions about generate_blog_post

What does the generate_blog_post tool do? +

Generate a full SEO-optimized blog post in Markdown from a topic and keywords. It is categorised as a Write tool in the WordPress AI Content System MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on generate_blog_post? +

Register the WordPress AI Content System MCP server in PolicyLayer and add a rule for generate_blog_post: 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 AI Content System. Nothing to install.

What risk level is generate_blog_post? +

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

Can I rate-limit generate_blog_post? +

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

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

generate_blog_post is provided by the WordPress AI Content System MCP server (ssolis-ti/wordpress_content_ai_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.