This record as markdown: /tools/io-favcrm-favcrm/delete-service-package.md
What delete_service_package does on FavCRM
AI agents call delete_service_package 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 |
|---|---|---|---|
packageId | string | Yes | Service package ID to delete |
Parameters from the server's own tool schema.
Why delete_service_package is rated Critical
This tool permanently removes a service package from the CRM. Service packages are core business entities that likely underpin pricing, bookings, and customer offerings. Deletion is irreversible and could break existing bookings, invoices, or customer subscriptions if the package is referenced elsewhere.
From the tool's definition Tool name contains 'delete' and description states 'Delete a service package by ID' — this is an irreversible deletion operation.
Attacks that exploit this kind of access
The rule that runs delete_service_package 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_service_package, this is the rule to start with:
delete_service_package 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_service_package call is checked against it from then on.
Questions about delete_service_package
Delete a service package by ID. 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_service_package accepts 1 parameter: packageId. Required: packageId. 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_service_package: 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_service_package 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_service_package 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_service_package. 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_service_package 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