update_post_type_field

Update a field on a post type schema. Changing fieldType or flipping required=true is blocked when posts already use the field unless force=true is passed.

SERVERFavCRM SOURCEhttps://api.favcrm.io/mcp

Medium RISK CLASS

Category Write

Parameters 102 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-favcrm-favcrm/update-post-type-field.md

WHAT IT DOES

What update_post_type_field does on FavCRM

AI agents use update_post_type_field 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
`force`	boolean	—	Override safety guards. Required to change fieldType or flip required=true on a field that already has data in posts.
`label`	string	—	Display label
`fields`	object	—	Child fields for fieldType="repeater".
`fieldId`	string	Yes	Field ID
`options`	object	—	For URL fields, { uploadable: true } enables file upload while preserving a URL string in meta.
`helpText`	object	—	Help text shown next to the input
`required`	boolean	—	Whether the field is required
`fieldType`	string	—	Field type
`sortOrder`	number	—	Sort order (lower = earlier)
`postTypeId`	string	Yes	Post type ID

Parameters from the server's own tool schema.

RISK

Why update_post_type_field is rated Medium

This is a Write operation: it modifies schema definitions (the post type structure) in a reversible manner. It is not Destructive because updates to schemas are generally undoable and the tool explicitly prevents dangerous changes unless force=true. It is not Execute or Financial.

From the tool's definition The tool updates a field on a post type schema, creating or modifying data structure. Key phrases: 'Update a field' and the note that 'Changing fieldType or flipping required=true is blocked...unless force=true is passed' indicates reversible schema…

Risk signalsHigh parameter count (10 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

update_post_type_field Rate-limited

update_post_type_field 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": {
    "update_post_type_field": {
      "limits": [
        {
          "counter": "update_post_type_field_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 FavCRM, apply this rule, and every update_post_type_field call is checked against it from then on.

FAQ

Questions about update_post_type_field

What does the update_post_type_field tool do? +

Update a field on a post type schema. Changing fieldType or flipping required=true is blocked when posts already use the field unless force=true is passed. 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.

What parameters does update_post_type_field accept? +

update_post_type_field accepts 10 parameters: force, label, fields, fieldId, options, helpText, required, fieldType, sortOrder, postTypeId. Required: fieldId, postTypeId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on update_post_type_field? +

Register the FavCRM MCP server in PolicyLayer and add a rule for update_post_type_field: 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.

What risk level is update_post_type_field? +

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

Can I rate-limit update_post_type_field? +

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

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

update_post_type_field 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.

KEEP EXPLORING

More on FavCRM, and thousands of servers like it.

This server

All 220 FavCRM tools →

Across the catalogue

aroflo_create_or_update_record on AroFlo MCP →team_manager_post_blackboard on Team Manager MCP → The MCP Attack Database →

Guides

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