delete_post_type
Delete a custom post type. Built-in types cannot be deleted. Fails if any posts of this type still exist — delete those first.
This record as markdown: /tools/io-favcrm-favcrm/delete-post-type.md
What delete_post_type does on FavCRM
AI agents call delete_post_type 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 |
|---|---|---|---|
postTypeId | string | Yes | Post type ID |
Parameters from the server's own tool schema.
Why delete_post_type is rated Critical
This tool permanently removes custom post type definitions from the CRM system. Deletion of data structures is irreversible and cannot be undone, making it Destructive rather than Write. The high severity reflects the organizational impact: deleting a post type could affect business workflows, content organization, and potentially trigger data loss if the operation cascades.
From the tool's definition Tool name 'delete_post_type' combined with description 'Delete a custom post type' explicitly indicates irreversible deletion.
Attacks that exploit this kind of access
The rule that runs delete_post_type 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_type, this is the rule to start with:
delete_post_type 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_type call is checked against it from then on.
Questions about delete_post_type
Delete a custom post type. Built-in types cannot be deleted. Fails if any posts of this type still exist — delete those first. 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_type accepts 1 parameter: postTypeId. Required: postTypeId. 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_type: 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_type 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_type 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_type. 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_type 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