set_incident_custom_field · InvGate Service Desk MCP

WHAT IT DOES

What set_incident_custom_field does on InvGate Service Desk

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

This tool modifies incident/request data by updating custom field values. It creates or changes data reversibly (the field value can be changed again), which fits the Write category. Severity is medium because while it modifies request records, it operates on a specific field rather than destructive deletion or financial transactions.

From the tool's definition Tool name 'set_incident_custom_field' and description 'Set the value(s) of a custom field on a request' indicate modification of existing data. The verb 'set' and action of assigning values to fields are characteristic of write operations.

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

set_incident_custom_field Rate-limited

set_incident_custom_field 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": {
    "set_incident_custom_field": {
      "limits": [
        {
          "counter": "set_incident_custom_field_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 set_incident_custom_field

What does the set_incident_custom_field tool do? +

Set the value(s) of a custom field 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 set_incident_custom_field? +

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

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

Can I rate-limit set_incident_custom_field? +

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

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

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