Skip to main content
Glama

Destroy a release policy

destroy_policy
DestructiveIdempotent

Destroy one of an organization's release policies by name. A change to a policy applies to releases not yet decided. Changing a policy's enforcement or settings never changes a decided evaluation, and a running policy evaluation keeps the checker and enforcement it started with. A running policy evaluation whose checker hasn't started yet uses the current settings. Removing a policy, or changing its checker, cancels its running policy evaluations, so releases that waited only on it go ahead. Confirm with the user first. Past evaluations stay on the releases they evaluated. Destroying a policy that is already gone changes nothing. Requires connecting a Valet account. Requires the Admin role.

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": {
      "policy": "<policy>"
    },
    "name": "destroy_policy"
  }
}

Input Schema

NameRequiredDescriptionDefault
policyYesThe policy's name, as list_policies reports it.
org_nameNoThe Valet organization the policy belongs to. Omit to use the organization the account joined first.

Output Schema

NameRequiredDescriptionDefault
orgYesName of the Valet organization the call acted in.
kindYesAlways policy: the kind of thing this tool destroys.
nameYesName of the release policy destroyed, as passed in policy.
already_goneNoTrue when the policy was already gone before the call, so nothing was destroyed. Absent when this call destroyed it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedOutput schema / properties / already_gone / description
      Previous value: -"True when the thing was already gone before the call, so nothing was destroyed. Absent when this call destroyed it."New value: +"True when the policy was already gone before the call, so nothing was destroyed. Absent when this call destroyed it."
    • changedOutput schema / properties / kind / description
      Previous value: -"What the thing was, such as channel, connector, or resource."New value: +"Always policy: the kind of thing this tool destroys."
    • addedOutput schema / properties / kind / enum
      Added value: +[
      +  "policy"
      +]
    • changedOutput schema / properties / name / description
      Previous value: -"Name of the thing the call destroyed, as the caller gave it."New value: +"Name of the release policy destroyed, as passed in policy."
  2. Changed5 schema fields changed
    • changedInput schema / properties / policy / description
      Previous value: -"Required. The policy's name, as list_policies reports it."New value: +"The policy's name, as list_policies reports it."
    • addedOutput schema / properties / already_gone / description
      Added value: +"True when the thing was already gone before the call, so nothing was destroyed. Absent when this call destroyed it."
    • addedOutput schema / properties / kind / description
      Added value: +"What the thing was, such as channel, connector, or resource."
    • addedOutput schema / properties / name / description
      Added value: +"Name of the thing the call destroyed, as the caller gave it."
    • addedOutput schema / properties / org / description
      Added value: +"Name of the Valet organization the call acted in."
  3. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": false,
      +  "properties": {
      +    "already_gone": {
      +      "type": "boolean"
      +    },
      +    "kind": {
      +      "type": "string"
      +    },
      +    "name": {
      +      "type": "string"
      +    },
      +    "org": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "org",
      +    "name",
      +    "kind"
      +  ],
      +  "type": "object"
      +}
  4. Added

TDQS

A4/5.0
Behavior4/5

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

Annotations already flag destructive=true and idempotent=true, and the description still adds real substance: removing a policy cancels its running evaluations and releases anything that waited only on it, past evaluations are preserved, an already-removed policy is a no-op, and Admin role is required. The surrounding sentences about how changes affect undecided releases describe set_policy behavior more than this tool, which slightly dilutes the value.

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?

Purpose is front-loaded and the operational sentences (confirmation, side effects, idempotency, auth) each carry weight. The mid-paragraph detail about policy changes applying to undecided releases is tangential for a destroy operation and could be trimmed.

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 an output schema present, return values need no explanation, and the description covers what an agent needs before calling: destructive and side-effect behavior, idempotent no-op case, confirmation requirement, and role/account prerequisites.

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 both parameters are already fully documented, including the org_name fallback. The description only echoes 'by name' and 'organization's', adding no syntax, matching rules, or failure behavior beyond the schema.

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 description opens with a specific verb and resource plus scope: 'Destroy one of an organization's release policies by name.' That immediately separates it from set_policy (modify) and from the other destroy_* siblings, which target channels, checkers, connectors and so on.

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

Usage Guidelines3/5

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

It supplies prerequisites (Valet account, Admin role) and an interaction rule ('Confirm with the user first'), and the contrast between changing a policy and removing it implies set_policy is the tool for settings changes. But it never states an explicit alternative or when-not condition such as 'use set_policy to disable enforcement instead of destroying'.

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.

Resources