create_category
Create a CMS post category (e.g. "Equipment", "Injection — Botox"). For sub-categories, use namespaced names — the table is flat.
This record as markdown: /tools/io-favcrm-favcrm/create-category.md
What create_category does on FavCRM
AI agents use create_category 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 |
|---|---|---|---|
name | string | Yes | Category name |
slug | string | — | Auto-generated from name if omitted. |
sortOrder | number | — | Sort order (lower = earlier) |
description | string | — | Description |
Parameters from the server's own tool schema.
Why create_category is rated Medium
This tool creates new category records in a CMS, which is a reversible write operation. It does not execute arbitrary code, delete data, move money, or retrieve sensitive information. The blast radius is minimal — categories are organizational metadata that can be renamed or deleted if misconfigured.
From the tool's definition Tool description states 'Create a CMS post category' — the verb 'Create' indicates data creation. The context (FavCRM service business platform with CMS features) and sibling tools confirm this is a write operation within a content management system.
Attacks that exploit this kind of access
The rule that runs create_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 create_category, this is the rule to start with:
create_category 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 create_category call is checked against it from then on.
Questions about create_category
Create a CMS post category (e.g. "Equipment", "Injection — Botox"). For sub-categories, use namespaced names — the table is flat. 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.
create_category accepts 4 parameters: name, slug, sortOrder, description. Required: name. 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 create_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.
create_category 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 create_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 create_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.
create_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.
This server
Across the catalogue