fields_status

cvrt-fields status: plugin version, definition counts per kind, whether ACF / Elementor / Elementor Pro are active, JSON sync state and JSON read error.

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

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/io-github-cvrt-jh-wordpress-mcp/fields-status.md

WHAT IT DOES

What fields_status does on Wordpress

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

RISK

Why fields_status is rated Low

Retrieves plugin metadata and configuration status without modifying data or triggering external operations.

From the tool's definition status, plugin version, definition counts, active plugins, sync state

Attacks that exploit this kind of access

RECOMMENDED RULE

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

fields_status Allowed

fields_status 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": {
    "fields_status": {}
  }
}

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

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

FAQ

Questions about fields_status

What does the fields_status tool do? +

cvrt-fields status: plugin version, definition counts per kind, whether ACF / Elementor / Elementor Pro are active, JSON sync state and JSON read error. It is categorised as a Read tool in the Wordpress MCP Server, which means it retrieves data without modifying state.

How do I enforce a policy on fields_status? +

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

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

Can I rate-limit fields_status? +

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

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

fields_status 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

editor_status on 010 Editor → The MCP Attack Database →

Guides

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