Illumio MCP Server

get-traffic-flows

Retrieve traffic flow records from Illumio PCE with filters for sources, destinations, services, and policy decisions. Aggregate by dimensions like process, FQDN, or rule to answer specific connectivity questions.

Instructions

Get traffic flows from the PCE with comprehensive filtering options

Input Schema

TableJSON Schema

Name	Required	Description
`end_date`	Yes	Ending datetime (YYYY-MM-DD or timestamp)
`group_by`	No	Dimensions to aggregate by. Any of: process, service_name, user, source, source_app, destination, dest_app, fqdn, ip_list, port, proto, policy, rule, direction. Fewer dimensions gives fewer, larger rows - e.g. ['process','fqdn'] answers 'which binary talks to which external name'. Defaults to a full per-flow breakdown.
`query_name`	No
`start_date`	Yes	Starting datetime (YYYY-MM-DD or timestamp)
`max_results`	No
`exclude_sources`	No	Sources to exclude (label/IP list/workload HREFs, FQDNs, IPs)
`include_sources`	No	Sources to include. Accepts label shorthand 'key=value' (e.g. 'app=vdi'), which the server resolves to a label HREF, as well as label/IP list/workload HREFs, FQDNs and IPs. Omit to match all sources.
`exclude_services`	No
`include_services`	No
`policy_decisions`	No
`exclude_destinations`	No	Destinations to exclude (label/IP list/workload HREFs, FQDNs, IPs)
`include_destinations`	No	Destinations to include. Accepts label shorthand 'key=value' (e.g. 'app=vdi'), as well as label/IP list/workload HREFs, FQDNs and IPs. Omit to match all destinations.
`exclude_workloads_from_ip_list_query`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed3 schema fields changedv0.8.0Sep 18, 2026

addedInput schema / properties / group_by

Added value: +{
+  "description": "Dimensions to aggregate by. Any of: process, service_name, user, source, source_app, destination, dest_app, fqdn, ip_list, port, proto, policy, rule, direction. Fewer dimensions gives fewer, larger rows - e.g. ['process','fqdn'] answers 'which binary talks to which external name'. Defaults to a full per-flow breakdown.",
+  "items": {
+    "type": "string"
+  },
+  "type": "array"
+}

changedInput schema / properties / include_destinations / description

Previous value: -"Destinations to include (label/IP list/workload HREFs, FQDNs, IPs)"New value: +"Destinations to include. Accepts label shorthand 'key=value' (e.g. 'app=vdi'), as well as label/IP list/workload HREFs, FQDNs and IPs. Omit to match all destinations."

changedInput schema / properties / include_sources / description

Previous value: -"Sources to include (label/IP list/workload HREFs, FQDNs, IPs)"New value: +"Sources to include. Accepts label shorthand 'key=value' (e.g. 'app=vdi'), which the server resolves to a label HREF, as well as label/IP list/workload HREFs, FQDNs and IPs. Omit to match all sources."

Addedv1.0.0Jan 2, 2026

TDQS

C2.7/5.0

Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It indicates a read operation via 'Get' but does not mention result size, pagination, time range behavior, defaults, or any side effects. For a tool with 13 parameters and no output schema, this leaves significant behavioral uncertainty.

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

Conciseness4/5

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

The description is a single, tight sentence with no filler, front-loading the core action and resource. It loses a point only because its brevity sacrifices useful context, but as written it is efficiently structured.

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

Completeness2/5

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

Given the tool's complexity (13 parameters, 2 required, no annotations, no output schema), a one-sentence description is insufficient. It does not explain default behavior, how results are returned, the meaning of grouping, or how this relates to get-traffic-flows-summary, so an agent is left without key operational context.

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

Parameters2/5

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

Schema description coverage is only 54%, and the description adds no parameter-specific meaning beyond the generic phrase 'comprehensive filtering options'. It does not compensate for the undocumented parameters such as query_name, max_results, policy_decisions, or include/exclude_services.

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?

The description uses a clear verb and resource ('Get traffic flows from the PCE') and signals the main capability (comprehensive filtering options). It clearly identifies what the tool does, but it does not differentiate it from the sibling get-traffic-flows-summary, so it falls short of a 5.

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

Usage Guidelines2/5

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

There is no guidance on when to use this tool versus the closely related get-traffic-flows-summary, nor any exclusions or alternative suggestions. 'Comprehensive filtering options' hints at a use case, but the description fails to state when an agent should pick this tool over its sibling.

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

Deploy Server

get-traffic-flows

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools