delete_post
Delete a CMS post by ID. Soft-deleted posts can be restored with restore_post.
This record as markdown: /tools/io-favcrm-favcrm/delete-post.md
What delete_post does on FavCRM
AI agents call delete_post 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 |
|---|---|---|---|
postId | string | Yes | The post ID |
Parameters from the server's own tool schema.
Why delete_post is rated Critical
Although the description mentions soft-deletion and restore_post capability, the primary action is irreversible deletion of data (a CMS post). This is a destructive operation that removes content from the system. In a CRM context managing customer-facing content, deletion of posts has significant business impact.
From the tool's definition Tool name 'delete_post' explicitly performs deletion. Description states 'Delete a CMS post by ID' and notes soft-deletion with restoration capability, indicating irreversible removal of published content.
Attacks that exploit this kind of access
The rule that runs delete_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 delete_post, this is the rule to start with:
delete_post 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 delete_post call is checked against it from then on.
Questions about delete_post
Delete a CMS post by ID. Soft-deleted posts can be restored with restore_post. 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.
delete_post accepts 1 parameter: postId. Required: 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 delete_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.
delete_post 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 delete_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.
Set action: deny in the PolicyLayer policy for delete_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.
delete_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.
More on FavCRM, and thousands of servers like it.
Across the catalogue