Skip to main content
Glama

Get cluster security posture

get_cluster_security_posture
Read-only

Read one cluster's security posture detail. report picks it: access (the cluster's Kubernetes access findings, such as standing cluster-admin grants or grants past the access policy, each with its remediation, and every check that could not be evaluated; the twin of ankra security access; grantee emails are withheld) or benchmark_resources (the Kubernetes objects failing one compliance control, each with the Ankra add-on or manifest that deploys it and its stack; the twin of ankra security benchmarks resources; needs check_id, and benchmark_id unless source is config_audit; take both from get_compliance_reports). An unknown is not a pass. benchmark_resources reads the cluster live and fails when its agent is unreachable. Read-only; needs security.read. For the benchmark totals use get_compliance_reports; for NetworkPolicy exposure use get_cluster_network_policy_overprivilege.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "report": "<report>"
    },
    "name": "get_cluster_security_posture"
  }
}

Input Schema

NameRequiredDescriptionDefault
reportYesWhich report to read.
sourceNobenchmark_resources: where the control comes from (default benchmark).
check_idNobenchmark_resources: the control's id.
cluster_idNoCluster id (UUID). Optional when the conversation is bound to a cluster.
benchmark_idNobenchmark_resources: the benchmark the control belongs to; required unless source is config_audit.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.8/5.0
Behavior5/5

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

Beyond readOnlyHint=true, the description discloses an auth requirement ("needs security.read"), a redaction rule ("grantee emails are withheld"), a live-read failure mode ("reads the cluster live and fails when its agent is unreachable"), and an interpretive rule ("An unknown is not a pass"). These are exactly the non-obvious traits an agent cannot get from annotations or schema.

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 core action and the report switch are front-loaded, and every clause carries information (no filler). Density is high, however: the two report modes are packed into nested parentheticals, which makes the passage slower to parse than a short bulleted breakdown would be.

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

Completeness5/5

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

There is no output schema, so the description carries the return-value burden and does so for both modes, including failure conditions and redactions. Auth needs, parameter sourcing, and sibling routing are all covered for a five-parameter read tool, leaving no material gap for an agent to call it correctly.

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 coverage is 100%, so the baseline is 3, but the description adds real meaning: it explains what each report enum value yields, why check_id and benchmark_id must be sourced from get_compliance_reports rather than invented, and how source changes benchmark_id optionality. It does not describe formats (UUIDs, id syntax) beyond the schema, so it stops short of a 5.

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 ("Read one cluster's security posture detail") and immediately disambiguates the two report modes: access findings (standing cluster-admin grants, policy violations, unevaluatable checks) versus benchmark_resources (objects failing one compliance control). The reader knows exactly what comes back in each case and can distinguish this from siblings like get_compliance_reports.

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

Usage Guidelines5/5

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

Explicit routing is provided for both directions: "For the benchmark totals use get_compliance_reports; for NetworkPolicy exposure use get_cluster_network_policy_overprivilege," plus the prerequisite chain (benchmark_resources needs check_id and benchmark_id unless source is config_audit, both taken from get_compliance_reports). The conditional dependency between parameters is spelled out rather than left to inference.

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.