Skip to main content
Glama
Sign In
alexgoller

Illumio MCP Server

by alexgoller
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

update-iplist

Update an existing PCE IP List by href or name, replacing IP ranges, FQDN entries, or description to keep policy data accurate.

Instructions

Update an existing IP List in the PCE. Provide either 'href' or 'name' (but not both) to identify the IP List. WRITE OPERATION: changes PCE state. In clients that gate tool calls (Claude Desktop, Claude Code), this pauses for the user to approve it -- the call has not failed and must not be retried while waiting.

Input Schema

NameRequiredDescriptionDefault
fqdnNoDeprecated alias for a single fqdns entry; use fqdns.
hrefNoHref of the IP List to update (e.g., /orgs/1/sec_policy/draft/ip_lists/123)
nameNoName of the IP List to update (alternative to href)
fqdnsNoReplaces the IP list's FQDN entries (like ip_ranges replaces the ranges). Omit to leave them unchanged.
ip_rangesNoNew list of IP ranges
descriptionNoNew description for the IP List (optional)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.13.1
    • changedInput schema / properties / fqdn / description
      Previous value: -"New Fully Qualified Domain Name (optional)"New value: +"Deprecated alias for a single fqdns entry; use fqdns."
    • addedInput schema / properties / fqdns
      Added value: +{
+  "description": "Replaces the IP list's FQDN entries (like ip_ranges replaces the ranges). Omit to leave them unchanged.",
+  "items": {
+    "anyOf": [
+      {
+        "type": "string"
+      },
+      {
+        "properties": {
+          "description": {
+            "type": "string"
+          },
+          "fqdn": {
+            "type": "string"
+          }
+        },
+        "required": [
+          "fqdn"
+        ],
+        "type": "object"
+      }
+    ]
+  },
+  "type": "array"
+}
  2. Changed2 schema fields changedv0.8.0
    • removedInput schema / oneOf
      Removed value: -[
-  {
-    "required": [
-      "href"
-    ]
-  },
-  {
-    "required": [
-      "name"
-    ]
-  }
-]
    • changedInput schema / properties / href / description
      Previous value: -"Href of the IP List to update"New value: +"Href of the IP List to update (e.g., /orgs/1/sec_policy/draft/ip_lists/123)"
  3. Addedv1.0.0

TDQS

A4/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries full burden and does meaningful work: it declares state mutation, warns that approval gating is expected client behavior, and explicitly forbids retrying while paused — a real failure mode this tool would otherwise cause. It omits permission prerequisites and what happens if the href/name does not resolve, so not exhaustive.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences: identity rule first, then the write/gating warning. Every clause is load-bearing and the retry warning is placed where an agent will read it before acting.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists but the tool returns a mutated resource, so return values go unmentioned; the pre-call behavior an agent most needs (approval pause, no retry) is covered. Sufficient for correct invocation, though error/not-found behavior is unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the replace-vs-omit semantics for fqdns and ip_ranges and the deprecated fqdn alias are already documented structurally. The description's only added parameter meaning is the href/name mutual exclusivity, which is genuinely useful but narrow against a 6-parameter tool.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Update an existing IP List in the PCE'), which unambiguously separates it from create-iplist/delete-iplist siblings by verb alone. It does not explicitly name which sibling to use for lookups, but the resource is precise.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives the concrete selection rule for its own two identifiers ('provide either href or name, but not both') and labels itself a write operation, which tells the agent when it is appropriate. It stops short of pointing to get-iplists for discovery or create-iplist for new lists, so no explicit alternative routing.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools