This record as markdown: /tools/io-favcrm-favcrm/update-category.md
What update_category does on FavCRM
AI agents use update_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 | — | Name |
slug | string | — | URL slug |
sortOrder | number | — | Sort order (lower = earlier) |
categoryId | string | Yes | Category ID |
description | object | — | Description |
Parameters from the server's own tool schema.
Why update_category is rated Medium
This tool modifies post category metadata within the CMS system. The action is reversible (a category can be changed again), creates no external side effects, does not execute arbitrary code, and does not delete or move money. It is a straightforward Write operation that updates the categorization of CMS content.
From the tool's definition The tool is named 'update_category' with description 'Update a CMS post category.' The verb 'update' indicates modification of existing data in a reversible manner.
Attacks that exploit this kind of access
The rule that runs update_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 update_category, this is the rule to start with:
update_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 update_category call is checked against it from then on.
Questions about update_category
Update a CMS post category. 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.
update_category accepts 5 parameters: name, slug, sortOrder, categoryId, description. 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 update_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.
update_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 update_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 update_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.
update_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