admin_export_content

Bereitet WordPress-Content für Export vor (Posts, Pages, etc.)

SERVERWordPress MCP Server SOURCEc-sakel/wp-mcp-server

Low RISK CLASS

Category Read

Parameters 00 required

Recommended Allowedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/c-sakel-wp-mcp-server/admin-export-content.md

WHAT IT DOES

What admin_export_content does on WordPress MCP Server

AI agents call admin_export_content to retrieve information from WordPress MCP Server without modifying anything. It is typically the context-gathering step in research, monitoring, and reporting workflows, before the agent takes action elsewhere.

RISK

Why admin_export_content is rated Low

The tool prepares/exports WordPress content (posts, pages, etc.), which is fundamentally a read operation — it retrieves and packages data for export without modifying or deleting it. Severity is medium because exporting content could expose sensitive data in bulk if misused by an AI agent.

From the tool's definition Bereitet WordPress-Content für Export vor (Posts, Pages, etc.) — 'prepares content for export', indicating a read/retrieval operation

Risk signalsAdmin/system-level operation

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs admin_export_content safely

PolicyLayer is an MCP gateway: it sits between your AI agents and WordPress MCP Server, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For admin_export_content, this is the rule to start with:

admin_export_content Allowed

admin_export_content is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "admin_export_content": {}
  }
}

ALLOW ONLY THIS TOOL → Instant setup, no code required.

The button opens the PolicyLayer dashboard: create your workspace, connect WordPress MCP Server, apply this rule, and every admin_export_content call is checked against it from then on.

FAQ

Questions about admin_export_content

What does the admin_export_content tool do? +

Bereitet WordPress-Content für Export vor (Posts, Pages, etc.). It is categorised as a Read tool in the WordPress MCP Server MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on admin_export_content? +

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

admin_export_content is a Read tool with low risk. Read-only tools are generally safe to allow by default.

Can I rate-limit admin_export_content? +

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

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

admin_export_content is provided by the WordPress MCP Server MCP server (c-sakel/wp-mcp-server). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on WordPress MCP Server, and thousands of servers like it.

This server

All 192 WordPress MCP Server tools →

Across the catalogue

The MCP Attack Database →

Guides

Roll out MCP under one policy →Data exfiltration →MCP token cost →