Skip to main content
Glama

Guard Waivers

codapult_guard_waivers

List and manage owner-attributed, time-limited exceptions for exact active finding fingerprints, so teams can track known issues without changing underlying rules.

Instructions

List or manage owner-attributed, time-limited exceptions tied to exact active finding fingerprints. Use list to inspect current waivers; add requires fingerprint, owner, expiry, and reason; renew/remove require waiver id and reason. Every mutation requires confirm=true and may be restricted by protected approval policy. Adding a waiver does not change the underlying rule.

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": "codapult_guard_waivers"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoExisting waiver ID; required for remove and renew.
rootNoProject path or workspace root.
issueNoOptional URL tracking the exception.
ownerNoPerson or team responsible for the exception; required for add.
actionNoOperation to perform; list is read-only.list
reasonNoWhy the exception is needed; required for every mutation.
confirmNoMust be true before adding, removing, or renewing a waiver.
expires_atNoExpiry timestamp with timezone; required for add and optionally updates expiry on renew.
fingerprintNoExact finding fingerprint from a Guard report; required for add.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed8 schema fields changedv0.13.2
    • addedInput schema / properties / action / description
      Added value: +"Operation to perform; list is read-only."
    • addedInput schema / properties / confirm / description
      Added value: +"Must be true before adding, removing, or renewing a waiver."
    • addedInput schema / properties / expires_at / description
      Added value: +"Expiry timestamp with timezone; required for add and optionally updates expiry on renew."
    • addedInput schema / properties / fingerprint / description
      Added value: +"Exact finding fingerprint from a Guard report; required for add."
    • addedInput schema / properties / id / description
      Added value: +"Existing waiver ID; required for remove and renew."
    • addedInput schema / properties / issue / description
      Added value: +"Optional URL tracking the exception."
    • addedInput schema / properties / owner / description
      Added value: +"Person or team responsible for the exception; required for add."
    • addedInput schema / properties / reason / description
      Added value: +"Why the exception is needed; required for every mutation."
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does disclose key traits: every mutation requires confirm=true, mutations may be blocked by protected approval policy, and waivers are owner-attributed and time-limited. It omits what list returns and whether removal is reversible, so not fully transparent.

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

Conciseness5/5

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

Four tight sentences: purpose first, then per-action requirements, then the mutation gate, then the semantic caveat. No filler and the most important constraints are front-loaded.

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 9-parameter, no-annotation, no-output-schema mutation tool, the description covers action semantics, required fields per action, the confirm gate, and policy restrictions. What list returns and how ids relate to fingerprints remain unstated, which is the main residual gap.

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 baseline is 3, but the description adds action-conditional requiredness (fingerprint/owner/expiry/reason for add; id and reason for renew/remove) that the schema cannot express since required is empty. This materially helps an agent avoid missing-parameter errors.

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 resource (owner-attributed, time-limited exceptions keyed to exact active finding fingerprints) plus the full action set (list/add/remove/renew). This is clearly distinguishable from siblings like governance, audit, and review, which do not deal with per-finding exceptions.

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?

Gives per-action guidance: list to inspect, add requires fingerprint/owner/expiry/reason, renew/remove require id and reason. It also clarifies the semantic boundary that adding a waiver does not change the underlying rule. It stops short of naming when to prefer this over governance or review workflows, so no explicit alternative routing.

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