Skip to main content
Glama
alexgoller

Illumio MCP Server

by alexgoller
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

update-ruleset

Update an existing ruleset to change its scopes, description, or enabled status. Identify the ruleset by href or name to modify the security policy.

Instructions

Update an existing ruleset in the PCE. Provide either 'href' or 'name' (but not both) to identify the ruleset. 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

TableJSON Schema
NameRequiredDescriptionDefault
hrefNoHref of the ruleset to update (e.g., /orgs/1/sec_policy/active/rule_sets/123)
nameNoName of the ruleset to update (alternative to href)
scopesNoNew scopes for the ruleset. Each scope is an array of label identifiers (either href strings like '/orgs/1/labels/42', or key=value strings like 'role=web', or objects with href property).
enabledNoWhether the ruleset is enabled
descriptionNoNew description for the ruleset

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.8.0
    • removedInput schema / oneOf
      Removed value: -[
-  {
-    "required": [
-      "href"
-    ]
-  },
-  {
-    "required": [
-      "name"
-    ]
-  }
-]
    • changedInput schema / properties / href / description
      Previous value: -"Href of the ruleset to update"New value: +"Href of the ruleset to update (e.g., /orgs/1/sec_policy/active/rule_sets/123)"
    • changedInput schema / properties / scopes / description
      Previous value: -"New scopes for the ruleset"New value: +"New scopes for the ruleset. Each scope is an array of label identifiers (either href strings like '/orgs/1/labels/42', or key=value strings like 'role=web', or objects with href property)."
    • addedInput schema / properties / scopes / items / items / description
      Added value: +"Label identifier - can be a string (href or key=value) or an object with href property"
    • removedInput schema / properties / scopes / items / items / oneOf
      Removed value: -[
-  {
-    "description": "Label href or key=value string",
-    "type": "string"
-  },
-  {
-    "properties": {
-      "href": {
-        "description": "Label href",
-        "type": "string"
-      }
-    },
-    "required": [
-      "href"
-    ],
-    "type": "object"
-  }
-]
  2. Addedv1.0.0

TDQS

A4.6/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden and does so well. It explicitly labels the operation as a WRITE OPERATION that changes PCE state, and it warns that in gated clients the call pauses for user approval and must not be retried. This is valuable behavioral context beyond the schema.

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?

The description is compact and front-loaded: it states the operation, then the key identifier constraint, then the critical write/approval behavior. Every sentence contributes necessary information with no filler.

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?

For a mutating tool with no annotations and no output schema, the description covers the main things an agent needs: what it updates, how to identify the target, and the approval-pause behavior. It could go further by explaining whether unspecified fields are left unchanged and what the response contains, but the core invocation guidance is complete.

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

Parameters4/5

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

Schema description coverage is 100%, so the baseline is 3. The description adds meaningful value by stating that either 'href' or 'name' must be provided but not both, which is a critical constraint not evident from the schema alone.

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

Purpose5/5

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

The description clearly states the tool updates an existing ruleset in the PCE, using a specific verb and resource. This distinguishes it from sibling tools like create-ruleset and delete-ruleset without requiring the schema.

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?

It gives clear usage context: updating an existing ruleset, rather than creating or deleting one. It does not explicitly name alternatives or provide when-not-to-use guidance, but the 'existing' qualifier and write-operation warning make the intended use clear.

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