create_incident_spontaneous_approval

WHAT IT DOES

What create_incident_spontaneous_approval does on InvGate Service Desk

AI agents use create_incident_spontaneous_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 create_incident_spontaneous_approval needs a policy

This tool creates (writes) a new approval entity within the service desk system. While it modifies state, the operation is reversible (approvals can typically be cancelled, as evidenced by the sibling tool 'cancel_incident_approval').

From the tool's definition Tool name contains 'create' and description states 'Create a spontaneous approval on a request', indicating creation of a new approval record.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

create_incident_spontaneous_approval Rate-limited

create_incident_spontaneous_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": {
    "create_incident_spontaneous_approval": {
      "limits": [
        {
          "counter": "create_incident_spontaneous_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 create_incident_spontaneous_approval

What does the create_incident_spontaneous_approval tool do? +

Create a spontaneous approval 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 create_incident_spontaneous_approval? +

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

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

Can I rate-limit create_incident_spontaneous_approval? +

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

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

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