update_post_type
Update a custom post type. Built-in types (blog_post, page) cannot be modified.
This record as markdown: /tools/io-favcrm-favcrm/update-post-type.md
What update_post_type does on FavCRM
AI agents use update_post_type 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 |
|---|---|---|---|
icon | object | — | Icon name or URL |
label | string | — | Display label |
sortOrder | number | — | Sort order (lower = earlier) |
postTypeId | string | Yes | Post type ID |
labelPlural | string | — | Plural display label |
supportsBlocks | boolean | — | Allow content blocks (rich body) |
supportsExcerpt | boolean | — | Allow an excerpt field |
supportsNesting | boolean | — | Allow parent/child nesting |
supportsCategories | boolean | — | Allow categories on this post type |
supportsFeaturedImage | boolean | — | Allow a featured image |
Parameters from the server's own tool schema.
Why update_post_type is rated Medium
This tool creates or modifies data reversibly. It updates post type definitions, which is a data modification operation. The severity is medium because modifying post types could affect content structure and display across the CRM system, but the operation is reversible (post type definitions can be changed back). The restriction that built-in types cannot be modified limits the blast radius.
From the tool's definition update_post_type performs an update operation on a custom post type, modifying its configuration or properties
Risk signalsHigh parameter count (10 properties)
Attacks that exploit this kind of access
The rule that runs update_post_type 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, this is the rule to start with:
update_post_type 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 update_post_type call is checked against it from then on.
Questions about update_post_type
Update a custom post type. Built-in types (blog_post, page) cannot be modified. 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.
update_post_type accepts 10 parameters: icon, label, sortOrder, postTypeId, labelPlural, supportsBlocks, supportsExcerpt, supportsNesting, supportsCategories, supportsFeaturedImage. Required: postTypeId. 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 update_post_type: 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.
update_post_type 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 update_post_type 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 update_post_type. 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.
update_post_type 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