wordpress_import_content · WordPress MCP Server MCP

WHAT IT DOES

What wordpress_import_content does on WordPress MCP Server

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

Importing content is a reversible write operation (imported items can be edited or deleted afterward). It creates or modifies data in the WordPress system. Severity is high because uncontrolled content imports could flood a site with malicious or spam content, but the operation itself is not destructive (items remain editable/removable) nor financial.

From the tool's definition Tool name indicates 'import_content' — a write operation that creates or modifies content in WordPress. Description is empty, limiting direct confirmation of scope, but the name strongly implies bulk content creation/modification.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

wordpress_import_content Rate-limited

wordpress_import_content 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_import_content": {
      "limits": [
        {
          "counter": "wordpress_import_content_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_import_content

What does the wordpress_import_content tool do? +

wordpress_import_content. 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_import_content? +

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

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

Can I rate-limit wordpress_import_content? +

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

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

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