create_service_category
Create a service category (e.g. "Treatments", "Classes") to group bookable services.
This record as markdown: /tools/io-favcrm-favcrm/create-service-category.md
What create_service_category does on FavCRM
AI agents use create_service_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 |
sortOrder | number | — | Sort order (lower = earlier) |
description | string | — | Description |
Parameters from the server's own tool schema.
Why create_service_category is rated Medium
Creating a service category in a CRM is a write operation that adds new metadata to organize services. It is reversible (the category can be deleted) and poses minimal risk even if misused by an agent—the worst outcome would be organizational clutter or incorrect categorization, with no data destruction, code execution, or financial impact.
From the tool's definition Tool name 'create_service_category' and description 'Create a service category' indicate data creation. This is reversible (categories can be deleted or modified later) and involves creating a configuration/categorization structure rather than executing code…
Attacks that exploit this kind of access
The rule that runs create_service_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_service_category, this is the rule to start with:
create_service_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_service_category call is checked against it from then on.
Questions about create_service_category
Create a service category (e.g. "Treatments", "Classes") to group bookable services. 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_service_category accepts 3 parameters: name, 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_service_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_service_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_service_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_service_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_service_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