fields_sync_definition
Copy a JSON-sourced definition into the database. Only JSON definitions can be synced.
This record as markdown: /tools/io-github-cvrt-jh-wordpress-mcp/fields-sync-definition.md
What fields_sync_definition does on Wordpress
AI agents use fields_sync_definition 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.
Why fields_sync_definition is rated Medium
Syncs JSON field definitions into the database, a reversible write operation.
From the tool's definition Copy a JSON-sourced definition into the database
Attacks that exploit this kind of access
The rule that runs fields_sync_definition 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_sync_definition, this is the rule to start with:
fields_sync_definition 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.
The button opens the PolicyLayer dashboard: create your workspace, connect Wordpress, apply this rule, and every fields_sync_definition call is checked against it from then on.
Questions about fields_sync_definition
Copy a JSON-sourced definition into the database. Only JSON definitions can be synced. 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.
Register the Wordpress MCP server in PolicyLayer and add a rule for fields_sync_definition: 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_sync_definition is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.
Yes. Add a rate_limit block to the fields_sync_definition 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_sync_definition. 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_sync_definition 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