Delete the value of a custom field on a request.
AI agents call delete_incident_custom_field 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.
This tool permanently removes custom field data from incidents/requests in a service desk system. Deletion of data is irreversible and cannot be undone through normal tool operations, making it Destructive rather than Write.
From the tool's definition Tool name contains 'delete' and description states 'Delete the value of a custom field on a request.' The verb 'delete' combined with removal of data from a production service desk system indicates irreversible data destruction.
Attacks that exploit this kind of access
Delete the value of a custom field on a request. 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 delete_incident_custom_field: 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.
delete_incident_custom_field 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_incident_custom_field 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_incident_custom_field. 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_incident_custom_field 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 →