replace_post_block

Replace a single block at the given index (0-based). Avoids fetching the full post and re-sending all blocks via update_post.

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

Medium RISK CLASS

Category Write

Parameters 33 required

Recommended Rate-limitedsee the rule below

Registry record Grade F, identity unverified Pull the record →

This record as markdown: /tools/io-favcrm-favcrm/replace-post-block.md

WHAT IT DOES

What replace_post_block does on FavCRM

AI agents use replace_post_block 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
`block`	object	Yes	Replacement block
`index`	integer	Yes	0-based index of the block to replace
`postId`	string	Yes	The post ID

Parameters from the server's own tool schema.

RISK

Why replace_post_block is rated Medium

This tool modifies post content by replacing a block at a specified index. This is a Write operation because it creates or modifies data reversibly — the previous block state can be recovered or the operation undone through subsequent writes or system rollback. It does not irreversibly delete data (Destructive), execute arbitrary code (Execute), or involve financial transactions (Financial).

From the tool's definition Tool name 'replace_post_block' and description 'Replace a single block at the given index' indicates modification of existing content. The term 'replace' denotes reversible data alteration.

Attacks that exploit this kind of access

RECOMMENDED RULE

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

replace_post_block Rate-limited

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

FAQ

Questions about replace_post_block

What does the replace_post_block tool do? +

Replace a single block at the given index (0-based). Avoids fetching the full post and re-sending all blocks via update_post. 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 replace_post_block accept? +

replace_post_block accepts 3 parameters: block, index, postId. Required: block, index, postId. The full parameter table on this page comes from the server's own tool schema.

How do I enforce a policy on replace_post_block? +

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

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

Can I rate-limit replace_post_block? +

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

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

replace_post_block 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

team_manager_post_blackboard on Team Manager MCP → The MCP Attack Database →

Guides

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