Promote a request to a major incident.
AI agents use promote_incident_to_major to create or update resources in InvGate Service Desk — usually the action step of a workflow, after the agent has gathered context. Every call changes real data in your InvGate Service Desk environment.
Promoting an incident to major status modifies the incident record and can trigger automated workflows, notifications, and resource escalation. However, the change is reversible (can be demoted back) and does not delete data or execute arbitrary code. It falls under Write category as a data modification action.
From the tool's definition Tool name 'promote_incident_to_major' and description 'Promote a request to a major incident' indicate modification of incident status/classification.
Attacks that exploit this kind of access
Promote a request to a major incident. It is categorised as a Write tool in the InvGate Service Desk MCP Server, which means it can create or modify data. Consider rate limits to prevent runaway writes.
Register the InvGate Service Desk MCP server in PolicyLayer and add a rule for promote_incident_to_major: 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.
promote_incident_to_major 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 promote_incident_to_major 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 promote_incident_to_major. 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.
promote_incident_to_major 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 →