Cancel an approval.
AI agents call cancel_incident_approval to permanently remove resources in InvGate Service Desk — typically in cleanup and lifecycle workflows. It does its job in a single call, and there is no undo.
Cancelling an approval removes or invalidates an existing approval record in the workflow. This is effectively irreversible — once cancelled, the approval state is destroyed and the workflow must be restarted or re-approved. This is more severe than a simple write/update, as it cannot be trivially undone and can block or derail incident resolution workflows.
From the tool's definition 'Cancel an approval' — cancelling an approval is an irreversible action that voids an existing approval decision/workflow state
Attacks that exploit this kind of access
Cancel an approval. It is categorised as a Destructive tool in the InvGate Service Desk MCP Server, which means it can permanently delete or destroy data. Block by default and require explicit approval.
Register the InvGate Service Desk MCP server in PolicyLayer and add a rule for cancel_incident_approval: 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 InvGate Service Desk. Nothing to install.
cancel_incident_approval 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_incident_approval 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_incident_approval. 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_incident_approval is provided by the InvGate Service Desk MCP server (oci:ghcr.io/tracegazer/invgate-service-desk-mcp:0.2.0). 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 →