Cancel a change approval group.
AI agents call cancel_change_approval_group to permanently remove resources in Freshservice MCP Server — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Cancelling a change approval group in an ITSM platform like Freshservice is a destructive, hard-to-reverse action. It voids the approval workflow associated with a change request, potentially allowing unapproved changes to proceed or breaking the change management process. This cannot be simply undone without recreating the approval group and restarting the approval process.
From the tool's definition 'Cancel a change approval group' — cancelling an approval group removes/voids the approval process irreversibly
Attacks that exploit this kind of access
Cancel a change approval group. It is categorised as a Destructive tool in the Freshservice MCP Server MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the Freshservice MCP Server MCP server in PolicyLayer and add a rule for cancel_change_approval_group: 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 Freshservice MCP Server. Nothing to install.
cancel_change_approval_group 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 cancel_change_approval_group 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 cancel_change_approval_group. 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.
cancel_change_approval_group is provided by the Freshservice MCP Server MCP server (leemangold/freshservice_mcp). PolicyLayer sits as a proxy in front of this server to enforce policies before tool calls reach the server.
Every MCP server has a record like this.
Type a name, get the same breakdown: verified identity, auth posture, risk grade, capabilities, recommended policy.
Teams ship this data inside their own products. See what a licence covers →