fields_update_settings

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/fields-update-settings.md

WHAT IT DOES

What fields_update_settings does on Wordpress

AI agents use fields_update_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 fields_update_settings is rated Medium

Modifies settings and manages credentials; reversible but affects system security configuration.

From the tool's definition Update cvrt-fields settings, github_token write-only stored encrypted

Attacks that exploit this kind of access

RECOMMENDED RULE

The rule that runs fields_update_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 fields_update_settings, this is the rule to start with:

fields_update_settings Rate-limited

fields_update_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": {
    "fields_update_settings": {
      "limits": [
        {
          "counter": "fields_update_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 fields_update_settings call is checked against it from then on.

FAQ

Questions about fields_update_settings

What does the fields_update_settings tool do? +

Update cvrt-fields settings. github_token is write-only and stored encrypted; a blank or omitted token keeps the stored one. clear_github_token: true deletes it. Returns the settings as fields_get_settings does (token as { set }). 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 fields_update_settings? +

Register the Wordpress MCP server in PolicyLayer and add a rule for fields_update_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 fields_update_settings? +

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

Can I rate-limit fields_update_settings? +

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

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

fields_update_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

aroflo_create_or_update_record on AroFlo MCP → The MCP Attack Database →

Guides

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