publish_to_wordpress · WordPress AI Content System MCP

WHAT IT DOES

What publish_to_wordpress does on WordPress AI Content System

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

Publishing a blog post to WordPress creates new, live content on a website that is immediately visible to the public and indexed by search engines. This is a Write operation (not Execute, because the specific outcome is deterministic: creating a post).

From the tool's definition Tool description: 'Publish a generated blog post to WordPress via REST API' — explicitly states publishing action, which creates new content in the live WordPress system.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

publish_to_wordpress Rate-limited

publish_to_wordpress 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": {
    "publish_to_wordpress": {
      "limits": [
        {
          "counter": "publish_to_wordpress_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 publish_to_wordpress

What does the publish_to_wordpress tool do? +

Publish a generated blog post to WordPress via REST API. 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 publish_to_wordpress? +

Register the WordPress AI Content System MCP server in PolicyLayer and add a rule for publish_to_wordpress: 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 publish_to_wordpress? +

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

Can I rate-limit publish_to_wordpress? +

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

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

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