delete_category
Delete a CMS post category. Posts in the category are not deleted; they are simply unlinked.
This record as markdown: /tools/io-favcrm-favcrm/delete-category.md
What delete_category does on FavCRM
AI agents call delete_category 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 |
|---|---|---|---|
categoryId | string | Yes | Category ID |
Parameters from the server's own tool schema.
Why delete_category is rated Critical
This tool permanently deletes a category data structure, which is an irreversible operation. Although posts are not deleted, the category record is destroyed and cannot be recovered through normal means. This qualifies as Destructive rather than Write (which would be reversible modifications). The severity is medium because the blast radius is limited to category management; posts and customer data remain intact.
From the tool's definition 'Delete' a CMS post category—irreversible removal of the category itself, though posts remain unlinked.
Attacks that exploit this kind of access
The rule that runs delete_category 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_category, this is the rule to start with:
delete_category 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_category call is checked against it from then on.
Questions about delete_category
Delete a CMS post category. Posts in the category are not deleted; they are simply unlinked. 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_category accepts 1 parameter: categoryId. Required: categoryId. 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_category: 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_category 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_category 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_category. 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_category 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