remove_post_block
Remove the block at the given index (0-based). All subsequent blocks shift up by one.
This record as markdown: /tools/io-favcrm-favcrm/remove-post-block.md
What remove_post_block does on FavCRM
AI agents call remove_post_block to permanently remove resources in FavCRM, typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
| Parameter | Type | Required | Description |
|---|---|---|---|
index | integer | Yes | 0-based index of the block to remove |
postId | string | Yes | The post ID |
Parameters from the server's own tool schema.
Why remove_post_block is rated Critical
Removing a post block deletes content permanently with no indication of an undo mechanism. The structural reindexing of subsequent blocks further suggests this is a destructive, irreversible operation. High severity because misuse by an AI agent could silently delete published or draft content blocks.
From the tool's definition 'Remove the block at the given index' — permanently removes content; 'All subsequent blocks shift up by one' implies irreversible deletion of that block with structural side effects.
Attacks that exploit this kind of access
The rule that runs remove_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 remove_post_block, this is the rule to start with:
remove_post_block is removed from the agent's tool list entirely, so the agent never calls it. The rest of the server keeps working.
The button opens the PolicyLayer dashboard: create your workspace, connect FavCRM, apply this rule, and every remove_post_block call is checked against it from then on.
Questions about remove_post_block
Remove the block at the given index (0-based). All subsequent blocks shift up by one. It is categorised as a Destructive tool in the FavCRM MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
remove_post_block accepts 2 parameters: index, postId. Required: index, postId. 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 remove_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.
remove_post_block is a Destructive tool with critical risk. Critical-risk tools should be blocked by default and only enabled with explicit human approval.
Yes. Add a rate_limit block to the remove_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.
Set action: deny in the PolicyLayer policy for remove_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.
remove_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.
More on FavCRM, and thousands of servers like it.
Across the catalogue