fields_list_definitions
List all definitions of one kind from every source (database, JSON, PHP) with their _source.
This record as markdown: /tools/io-github-cvrt-jh-wordpress-mcp/fields-list-definitions.md
What fields_list_definitions does on Wordpress
AI agents call fields_list_definitions 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.
Why fields_list_definitions is rated Low
Tool retrieves and lists field definitions from multiple sources without modifying or executing any operations.
From the tool's definition List all definitions of one kind from every source with their _source.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs fields_list_definitions 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_list_definitions, this is the rule to start with:
fields_list_definitions is read-only, so it stays allowed. Everything else on the server is denied unless you say otherwise.
The button opens the PolicyLayer dashboard: create your workspace, connect Wordpress, apply this rule, and every fields_list_definitions call is checked against it from then on.
Questions about fields_list_definitions
List all definitions of one kind from every source (database, JSON, PHP) with their _source. It is categorised as a Read tool in the Wordpress MCP Server, which means it retrieves data without modifying state.
Register the Wordpress MCP server in PolicyLayer and add a rule for fields_list_definitions: 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.
fields_list_definitions is a Read tool with low risk. Read-only tools are generally safe to allow by default.
Yes. Add a rate_limit block to the fields_list_definitions 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.
Set action: deny in the PolicyLayer policy for fields_list_definitions. 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.
fields_list_definitions 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.
More on Wordpress, and thousands of servers like it.
This server
Across the catalogue