add_incident_collaborator · InvGate Service Desk MCP

WHAT IT DOES

What add_incident_collaborator does on InvGate Service Desk

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

This tool creates or modifies data (adds collaborators to an incident) but does not execute arbitrary code, delete data, or move money. The modification is reversible—collaborators can be removed.

From the tool's definition Tool name 'add_incident_collaborator' and description 'Request collaboration from one or more users on a request' indicate the tool modifies incident records by adding collaborators, which is a reversible change to request metadata.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_incident_collaborator Rate-limited

add_incident_collaborator 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": {
    "add_incident_collaborator": {
      "limits": [
        {
          "counter": "add_incident_collaborator_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 add_incident_collaborator

What does the add_incident_collaborator tool do? +

Request collaboration from one or more users 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 add_incident_collaborator? +

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

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

Can I rate-limit add_incident_collaborator? +

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

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

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