add_incident_observer · InvGate Service Desk MCP

WHAT IT DOES

What add_incident_observer does on InvGate Service Desk

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

The tool modifies request metadata by adding observer associations, which is a write operation rather than read-only. While low-risk in isolation (no data deletion or financial impact), it could be misused to add unauthorized observers to sensitive incidents, potentially exposing confidential information.

From the tool's definition Tool performs 'Add one or more users as observers' - a modification action that updates incident state by adding observer relationships to requests. This is a reversible data modification (users can be removed as observers).

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

add_incident_observer Rate-limited

add_incident_observer 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_observer": {
      "limits": [
        {
          "counter": "add_incident_observer_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_observer

What does the add_incident_observer tool do? +

Add one or more users as observers of 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_observer? +

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

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

Can I rate-limit add_incident_observer? +

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

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

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