request_incident_custom_approval · InvGate Service Desk MCP

WHAT IT DOES

What request_incident_custom_approval does on InvGate Service Desk

AI agents use request_incident_custom_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 request_incident_custom_approval needs a policy

This tool creates a new approval request on an incident, which is a write operation (adding a new approval record/workflow). It does not delete data, execute code, or move money. Misuse could trigger unintended approval workflows on incidents, but effects are reversible (approvals can be cancelled, as evidenced by the sibling tool cancel_incident_approval).

From the tool's definition 'Request a custom approval (by template) on a request' — initiates/creates an approval workflow on an incident

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

request_incident_custom_approval Rate-limited

request_incident_custom_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": {
    "request_incident_custom_approval": {
      "limits": [
        {
          "counter": "request_incident_custom_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 request_incident_custom_approval

What does the request_incident_custom_approval tool do? +

Request a custom approval (by template) on a request. 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 request_incident_custom_approval? +

Register the InvGate Service Desk MCP server in PolicyLayer and add a rule for request_incident_custom_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 request_incident_custom_approval? +

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

Can I rate-limit request_incident_custom_approval? +

Yes. Add a rate_limit block to the request_incident_custom_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 request_incident_custom_approval completely? +

Set action: deny in the PolicyLayer policy for request_incident_custom_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 request_incident_custom_approval? +

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