reject_incident_approval · InvGate Service Desk MCP

WHAT IT DOES

What reject_incident_approval does on InvGate Service Desk

AI agents use reject_incident_approval 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.

WHY IT NEEDS A POLICY

Why reject_incident_approval needs a policy

The tool performs a state transition on an approval record within the service desk system. While it changes data, the operation is reversible (an approval can typically be resubmitted or re-evaluated), placing it in the Write category rather than Destructive.

From the tool's definition Tool name 'reject_incident_approval' and description 'Reject an approval' indicate a state-change operation on an approval entity. This modifies the approval status from pending to rejected, which is a reversible write operation.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

reject_incident_approval Rate-limited

reject_incident_approval stays usable, but capped — an agent stuck in a loop can't make hundreds of changes a minute. Everything else on the server is denied unless you say otherwise.

View as policy code

policy.json

{
  "version": "1",
  "default": "deny",
  "tools": {
    "reject_incident_approval": {
      "limits": [
        {
          "counter": "reject_incident_approval_rate",
          "window": "minute",
          "max": 30,
          "scope": "grant"
        }
      ]
    }
  }
}

LIMIT THIS TOOL →

Instant setup, no code required.

PolicyLayer is an MCP gateway: every tool call is checked against your rule before it reaches InvGate Service Desk, so you can run agents against it safely.

FAQ

Questions about reject_incident_approval

What does the reject_incident_approval tool do? +

Reject an approval. 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.

How do I enforce a policy on reject_incident_approval? +

Register the InvGate Service Desk MCP server in PolicyLayer and add a rule for reject_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.

What risk level is reject_incident_approval? +

reject_incident_approval is a Write tool with medium risk. Write tools should be rate-limited to prevent accidental bulk modifications.

Can I rate-limit reject_incident_approval? +

Yes. Add a rate_limit block to the reject_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.

How do I block reject_incident_approval completely? +

Set action: deny in the PolicyLayer policy for reject_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.

What MCP server provides reject_incident_approval? +

reject_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.