Skip to main content
Glama

List security dispositions

list_security_dispositions
Read-only

List the vulnerability disposition policies of the organisation: each acknowledgement or accepted-risk decision with its selector (CVE, add-on scope), disposition, reason, expiry, expire-when-fixed flag, lifecycle status (active, expiring, fix_available, mitigated, unmatched, expired, revoked) and how many occurrences it currently matches. With scope repository_code, lists the Semgrep and Checkov finding dispositions the Ankra Pipelines image gate honours instead (repository, tool, rule, path, false_positive or accepted_risk, reason, who, when, expiry, status), optionally for one application_id or repository_id; statuses narrows it to active, expired or revoked (revoked ones are listed only when asked for). Read-only. Use it to review accepted risk before it expires and to find the policy_id update_security_disposition and revoke_security_disposition take.

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_dispositions"
  }
}

Input Schema

NameRequiredDescriptionDefault
pageNoPage number, starting at 1.
sortNoSort column: updated_at (default), created_at, expires_at, matched_occurrence_count, status, disposition.
orderNoasc or desc.
scopeNorepository_code to list code finding dispositions (image gate waivers) instead of vulnerability policies.
searchNoMatch CVE id, add-on, reason or the member who decided.
statusesNoOnly these lifecycle states: active, expiring, fix_available, mitigated, unmatched, expired, revoked.
page_sizeNoResults per page (default 50).
dispositionsNoOnly these dispositions: acknowledged, accepted_risk.
repository_idNoWith scope repository_code: only this pipeline repository (UUID).
application_idNoWith scope repository_code: only this application's pipeline repository (UUID).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / application_id
      Added value: +{
      +  "description": "With scope repository_code: only this application's pipeline repository (UUID).",
      +  "type": "string"
      +}
    • addedInput schema / properties / repository_id
      Added value: +{
      +  "description": "With scope repository_code: only this pipeline repository (UUID).",
      +  "type": "string"
      +}
    • addedInput schema / properties / scope
      Added value: +{
      +  "description": "repository_code to list code finding dispositions (image gate waivers) instead of vulnerability policies.",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

The 'Read-only' statement is consistent with readOnlyHint=true, and the description adds non-obvious behaviour beyond the annotation: revoked dispositions are returned only when explicitly requested, statuses filters the set, and the result shape changes entirely under scope=repository_code. It does not discuss pagination limits or default ordering beyond what the schema already declares, which keeps it from 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?

The purpose and the default (vulnerability policy) mode are front-loaded, with the alternate scope mode and the downstream-tool hint following in a logical order. The middle sentence is dense and run-on, packing two result shapes into one long clause chain, but nearly every clause carries information the agent needs.

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?

With 10 optional parameters, no required fields and no output schema, the description carries the burden of explaining what comes back – and it does so for both modes, enumerating the fields of each result shape. It also corrects the risk of calling it blind by naming the policy_id it produces for the update/revoke tools, so nothing essential is missing.

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 earns above baseline by explaining the cross-parameter interaction – that scope=repository_code switches the entity type, narrows statuses to active/expired/revoked, and makes application_id/repository_id applicable. That is genuine semantics the per-property schema text cannot convey, though some of it overlaps the schema's own 'With scope repository_code' notes.

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 first clause names a specific verb and resource ('List the vulnerability disposition policies of the organisation') and immediately enumerates the fields returned (selector, disposition, reason, expiry, status, match count). It also carves out a second, clearly delimited mode ('With scope repository_code, lists the Semgrep and Checkov finding dispositions'), so an agent can distinguish it from create_security_disposition, update_security_disposition, revoke_security_disposition and preview_security_disposition without opening any 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 states an explicit use case ('review accepted risk before it expires') and a concrete downstream purpose ('find the policy_id update_security_disposition and revoke_security_disposition take'), which routes the agent to the right follow-up tools. It does not explicitly say when to prefer this over preview_security_disposition or the other security-listing siblings, so a small gap remains.

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.