update_post

Update an existing CMS post (any post type). Only provided fields are changed.

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

Medium RISK CLASS

Category Write

Parameters 121 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.md

WHAT IT DOES

What update_post does on FavCRM

AI agents use update_post 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
`meta`	object	—	Custom field values; merged shallowly with existing meta. Use this for structured data, not excerpt.
`slug`	string	—	URL slug (must be unique per company+type).
`type`	string	—	Change post type (e.g. blog_post → treatment). Slug is re-checked for uniqueness under the new type.
`title`	string	—	Post title
`blocks`	array	—	Replaces the entire ordered block array. Use append_post_block / replace_post_block / remove_post_block / reorder_post_blocks for per-block edits. Each block: {
`postId`	string	Yes	The post ID
`status`	string	—	Post status
`tagIds`	array	—	Tag IDs to sync (replaces existing tags)
`excerpt`	string	—	Plain-text summary only — never JSON. Omit to leave unchanged.
`parentId`	object	—	Parent post ID for nested types.
`seoTitle`	string	—	SEO title override
`sortOrder`	number	—	Sort order (lower = earlier)

Parameters from the server's own tool schema.

RISK

Why update_post is rated Medium

This tool creates or modifies data reversibly within the CMS/content management system of the CRM. It updates posts without deleting them, making it a Write operation. Severity is medium because unauthorized post updates could damage business reputation, marketing content, or customer-facing information, but the changes are reversible and don't result in permanent loss or financial impact.

From the tool's definition Tool name 'update_post' and description 'Update an existing CMS post (any post type). Only provided fields are changed.' indicate data modification.

Risk signalsHigh parameter count (17 properties)

Attacks that exploit this kind of access

RECOMMENDED RULE

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

update_post Rate-limited

update_post 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": {
      "limits": [
        {
          "counter": "update_post_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 call is checked against it from then on.

FAQ

Questions about update_post

What does the update_post tool do? +

Update an existing CMS post (any post type). Only provided fields are changed. 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 accept? +

update_post accepts 12 parameters: meta, slug, type, title, blocks, postId, status, tagIds, excerpt, parentId, seoTitle, sortOrder. Required: postId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on update_post? +

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

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

Can I rate-limit update_post? +

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

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

update_post 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 →