restore_category
Restore a previously deleted CMS post category.
This record as markdown: /tools/io-favcrm-favcrm/restore-category.md
What restore_category does on FavCRM
AI agents use restore_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 |
|---|---|---|---|
categoryId | string | Yes | Category ID |
Parameters from the server's own tool schema.
Why restore_category is rated Medium
This tool modifies data by restoring a previously deleted category, making it a Write operation rather than Destructive. While it reverses a prior destructive action, the tool itself performs a constructive/restorative modification. The impact is moderate—restoring a category could affect content organization and visibility—but is reversible by deleting it again.
From the tool's definition Tool name 'restore_category' and description 'Restore a previously deleted CMS post category' indicate the tool reverses a deletion by restoring data.
Attacks that exploit this kind of access
The rule that runs restore_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 restore_category, this is the rule to start with:
restore_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 restore_category call is checked against it from then on.
Questions about restore_category
Restore a previously deleted 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.
restore_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 restore_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.
restore_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 restore_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 restore_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.
restore_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