seo_export_settings

Export every csm_* option as a flat { csm_name: value } map. Secrets are masked as { set: boolean }.

SERVERWordpress SOURCE@cavort-it-systems/wordpress-mcp

Medium RISK CLASS

Category Write

Parameters 00 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-github-cvrt-jh-wordpress-mcp/seo-export-settings.md

WHAT IT DOES

What seo_export_settings does on Wordpress

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

RISK

Why seo_export_settings is rated Medium

An AI agent can call seo_export_settings faster than any human can review: one bad instruction and it creates or modifies resources in Wordpress by the hundred, each call as confident as the last.

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs seo_export_settings safely

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

seo_export_settings Rate-limited

seo_export_settings 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": {
    "seo_export_settings": {
      "limits": [
        {
          "counter": "seo_export_settings_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL → Instant setup, no code required.

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

FAQ

Questions about seo_export_settings

What does the seo_export_settings tool do? +

Export every csm_* option as a flat { csm_name: value } map. Secrets are masked as { set: boolean }. It is categorised as a Write tool in the Wordpress MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.

How do I enforce a policy on seo_export_settings? +

Register the Wordpress MCP server in PolicyLayer and add a rule for seo_export_settings: 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. Nothing to install.

What risk level is seo_export_settings? +

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

Can I rate-limit seo_export_settings? +

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

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

seo_export_settings is provided by the Wordpress MCP server (@cavort-it-systems/wordpress-mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.

KEEP EXPLORING

More on Wordpress, and thousands of servers like it.

This server

All 314 Wordpress tools →

Across the catalogue

The MCP Attack Database →

Guides

Govern customer-ops agents →Argument validation →Scoped token →