Skip to main content
Glama

List security workloads

list_security_workloads
Read-only

List the workloads carrying security findings across the fleet, one row per workload container image, with its cluster, namespace, add-on attribution, observed and actionable CVE counts by severity, known-exploited and fixable-severe counts, risk score and last scan. Read-only. Takes the same filters as list_security_findings; sort by risk_score (default), severity, known_exploited, fixable_severe, observed, actionable, last_scan or workload_name. Use it for 'which workload should we patch first'.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_security_workloads"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, starting at 1.
sortNoSort column: risk_score (default), priority, severity, last_scan, observed, actionable, fixable_severe, workload_name, image_ref, cluster_name, addon_attribution, known_exploited.
orderNoasc or desc.
searchNoMatch CVE id, package name, image or workload name.
fixableNotrue for findings with a fixed version available, false for those without.
statusesNoOnly these disposition states (open, acknowledged, accepted_risk, resolved). Default: open and acknowledged - the actionable set.
namespaceNoRestrict to one namespace.
page_sizeNoResults per page (default 50).
addon_slugNoRestrict to workloads attributed to one add-on.
cluster_idNoRestrict to one cluster (UUID).
severitiesNoOnly these severities (critical, high, medium, low, unknown).
known_exploitedNotrue to keep only CVEs in CISA's Known Exploited Vulnerabilities catalog.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, and the description restates 'Read-only', which is redundant but harmless. Beyond that it discloses the result grain and the full set of columns returned, which is genuinely valuable given there is no output schema. It does not cover pagination behaviour or default disposition filtering, keeping it below a 5.

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?

Front-loaded with purpose and grain, then read-only, then sort/filters, then the use case. The long field enumeration is dense but justified because there is no output schema. Minor waste in restating 'Read-only' after the annotation already says so.

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 12-parameter, zero-required, no-output-schema list tool, the description supplies the result shape, default sort, filter compatibility and a target question. Missing only small operational details such as default disposition scope and page-size behaviour, which the schema covers anyway.

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 coverage is 100%, so all 12 parameters are already documented, including the full sort enumeration and default status set. The description's sort list is a partial duplicate of the schema's (it omits priority, image_ref, cluster_name, addon_attribution, known_exploited placement) and adds little beyond the 'same filters as list_security_findings' cross-reference. Baseline 3 is appropriate.

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?

States a specific verb and resource ('List the workloads carrying security findings across the fleet') and nails the grain: one row per workload container image. It enumerates the returned fields (cluster, namespace, add-on attribution, CVE counts by severity, risk score, last scan), which distinguishes it clearly from siblings like list_security_findings, list_security_pods and list_security_namespaces.

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?

Explicitly frames the selection scenario: 'Use it for which workload should we patch first', which is a prioritisation use case distinct from raw finding listing. It also points at list_security_findings as the filter-compatible alternative. No explicit when-not or exclusion, so it falls short of a 5.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.