Illumio MCP Server
Related Servers
Alternatives to Illumio MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server that enables AI assistants to perform comprehensive AWS security analysis through natural language queries, bridging AI with AWS security services.2Apache 2.0
- AlicenseNot gradedqualityAmaintenanceA modular, multi-transport Model Context Protocol server that connects AI assistants to the CrowdStrike Falcon platform. Query NG-SIEM logs, triage alerts, inspect endpoints, manage detection rules, and audit cloud security posture — all through natural language.14MIT
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that connects AI assistants to MISP threat intelligence platforms. It enables threat intelligence search, IOC lookup, and event analysis through natural conversation.-
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that connects AI assistants to OpenCTI threat intelligence platforms. It enables natural language interaction for searching threat intelligence, analyzing reports, managing indicators, and monitoring connectors.-
- AlicenseNot gradedqualityDmaintenanceModel Context Protocol server that connects AI agents with CrowdStrike Falcon platform for intelligent security analysis and automation.MIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that connects AI agents to IBM Concert, enabling autonomous workflow health monitoring, incident diagnosis, auto-remediation, CVE triage, and Slack alerting through natural language.Apache 2.0
TDQS
Scored across 53 tools
The bulk of tools map cleanly to distinct resources (workloads, labels, IP lists, services, rulesets) with consistent resource+action separation. The main risk area is the cluster of traffic/analysis tools (get-traffic-flows, get-traffic-flows-summary, get-traffic-timeline, discover-process-egress, build-identity-graph, find-unmanaged-traffic, detect-lateral-movement-paths), which overlap in scope. Descriptions largely mitigate this by explicitly stating when to prefer one over another, so an agent can usually disambiguate.
Strong, predictable verb_noun snake_case pattern (get-/create-/update-/delete- + resource) throughout the CRUD tools. A handful of deviations exist (enforcement-readiness, compliance-check, ringfence-batch, register-pce-credentials, compare-draft-active) that don't follow the verb_noun template, and get-iplists plural clashes with create-iplist singular, but overall readability is high.
53 tools is very heavy and sits in the 'too many' band. The underlying domain (PCE workloads, labels, rulesets, rules, IP lists, services, traffic analytics, container/K8s, compliance, credentials) is genuinely broad, which justifies a large surface, but the count is still over-provisioned and increases selection cost for the agent.
Full CRUD lifecycle is covered for workloads, labels, IP lists, services, and rulesets, plus deny-rule create/update/delete and provisioning/comparison flows. The notable gap is allow 'sec' rules: update-sec-rule and delete-sec-rule exist but there is no create-sec-rule, so standalone allow rules can only be added implicitly via rulesets/ringfences. Events expose read-only access, which is reasonable for audit data.