reorder_post_blocks
Reorder blocks by passing block IDs in the desired order. The id list must contain every existing block id exactly once.
This record as markdown: /tools/io-favcrm-favcrm/reorder-post-blocks.md
What reorder_post_blocks does on FavCRM
AI agents use reorder_post_blocks 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 |
|---|---|---|---|
postId | string | Yes | The post ID |
orderedBlockIds | array | Yes | Block IDs in the desired order; must match the existing set exactly |
Parameters from the server's own tool schema.
Why reorder_post_blocks is rated Medium
Reordering is a reversible modification operation - it rearranges existing blocks without creating, deleting, or executing external operations. The constraint that 'the id list must contain every existing block id exactly once' suggests it's a structural reordering of content. This falls under Write category as it modifies data state reversibly.
From the tool's definition Tool description states 'Reorder blocks by passing block IDs in the desired order.' This modifies the sequence/arrangement of existing content blocks, which is a write operation that changes data state.
Risk signalsBulk/mass operation — affects multiple targets
Attacks that exploit this kind of access
The rule that runs reorder_post_blocks 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 reorder_post_blocks, this is the rule to start with:
reorder_post_blocks 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 reorder_post_blocks call is checked against it from then on.
Questions about reorder_post_blocks
Reorder blocks by passing block IDs in the desired order. The id list must contain every existing block id exactly once. 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.
reorder_post_blocks accepts 2 parameters: postId, orderedBlockIds. Required: postId, orderedBlockIds. 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 reorder_post_blocks: 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.
reorder_post_blocks 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 reorder_post_blocks 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 reorder_post_blocks. 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.
reorder_post_blocks 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