link_incident_to_external_entity · InvGate Service Desk MCP

WHAT IT DOES

What link_incident_to_external_entity does on InvGate Service Desk

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

This tool creates a relationship/association between an incident and an external entity. It modifies data by establishing a link, which is a reversible write operation. No code execution, deletion, or financial implications are indicated. Confidence is moderate because 'external entity' is vague and could imply broader side effects, but the core action is creating a link/association.

From the tool's definition "Link a request to an external entity"

Attacks that exploit this kind of access

Recommended rule Ready

Verdict

link_incident_to_external_entity Rate-limited

link_incident_to_external_entity 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": {
    "link_incident_to_external_entity": {
      "limits": [
        {
          "counter": "link_incident_to_external_entity_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 link_incident_to_external_entity

What does the link_incident_to_external_entity tool do? +

Link a request to an external entity. 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 link_incident_to_external_entity? +

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

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

Can I rate-limit link_incident_to_external_entity? +

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

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

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