relate_incident_to_cis_by_keyword · InvGate Service Desk MCP

WHAT IT DOES

What relate_incident_to_cis_by_keyword does on InvGate Service Desk

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

This tool writes new associations between an incident/request and configuration items (CIs). It modifies data by creating relationships, but these are likely reversible (relationships can be removed). The blast radius is medium because a broad keyword could inadvertently link a request to many unintended CIs, potentially causing confusion or incorrect asset tracking.

From the tool's definition 'Relate a request to every CI that matches a keyword' — creates relationships between a request and multiple configuration items

Risk signalsBulk/mass operation — affects multiple targets

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

relate_incident_to_cis_by_keyword Rate-limited

relate_incident_to_cis_by_keyword 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": {
    "relate_incident_to_cis_by_keyword": {
      "limits": [
        {
          "counter": "relate_incident_to_cis_by_keyword_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 relate_incident_to_cis_by_keyword

What does the relate_incident_to_cis_by_keyword tool do? +

Relate a request to every CI that matches a keyword. 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 relate_incident_to_cis_by_keyword? +

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

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

Can I rate-limit relate_incident_to_cis_by_keyword? +

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

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

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