reorder_post_type_fields
Reorder fields on a post type. Pass field IDs in the desired display order; sortOrder is updated to match.
This record as markdown: /tools/io-favcrm-favcrm/reorder-post-type-fields.md
What reorder_post_type_fields does on FavCRM
AI agents use reorder_post_type_fields to create or update resources in FavCRM, usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your FavCRM environment.
| Parameter | Type | Required | Description |
|---|---|---|---|
postTypeId | string | Yes | Post type ID |
orderedFieldIds | array | Yes | Field IDs in the desired order |
Parameters from the server's own tool schema.
Why reorder_post_type_fields is rated Medium
The tool updates post type field ordering (sortOrder), which modifies the structure/metadata of the system. This is a Write operation (reversible modification of configuration data), not a Read (no query-only), Execute (no code/command execution), Destructive (sortOrder changes are reversible), or Financial operation.
From the tool's definition Tool performs 'Reorder fields on a post type' and 'sortOrder is updated to match', indicating it modifies the configuration/schema of a post type by changing field ordering. This is a reversible data modification operation.
Attacks that exploit this kind of access
The rule that runs reorder_post_type_fields safely
PolicyLayer is an MCP gateway: it sits between your AI agents and FavCRM, and checks every tool call against a rule you set before the call runs. Nothing changes on the server itself. For reorder_post_type_fields, this is the rule to start with:
reorder_post_type_fields 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 FavCRM, apply this rule, and every reorder_post_type_fields call is checked against it from then on.
Questions about reorder_post_type_fields
Reorder fields on a post type. Pass field IDs in the desired display order; sortOrder is updated to match. It is categorised as a Write tool in the FavCRM MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
reorder_post_type_fields accepts 2 parameters: postTypeId, orderedFieldIds. Required: postTypeId, orderedFieldIds. The full parameter table on this page comes from the server's own tool schema.
Register the FavCRM MCP server in PolicyLayer and add a rule for reorder_post_type_fields: 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 FavCRM. Nothing to install.
reorder_post_type_fields 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 reorder_post_type_fields 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 reorder_post_type_fields. 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.
reorder_post_type_fields is provided by the FavCRM MCP server (https://api.favcrm.io/mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
More on FavCRM, and thousands of servers like it.
This server
Across the catalogue