Skip to main content
Glama

Revoke security disposition

revoke_security_disposition
Destructive

Revoke a disposition (security.manage): every finding it covered returns to open on the next read, and the disposition stays on record as revoked with the reason. For a repository_code disposition the Ankra Pipelines image gate blocks on the finding again from its next run. Use it when accepted risk is no longer acceptable or an acknowledgement or false-positive call was wrong.

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_id": "<policy_id>",
      "reason": "<reason>"
    },
    "name": "revoke_security_disposition"
  }
}

Input Schema

NameRequiredDescriptionDefault
scopeNorepository_code when policy_id is a code finding disposition; optional, since the id is recognised either way.
reasonYesWhy the policy is revoked. Required; recorded on the audit trail.
policy_idYesPolicy id (UUID) from list_security_dispositions, or a repository_code disposition id from list_security_dispositions with scope repository_code.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / policy_id / description
      Previous value: -"Policy id (UUID) from list_security_dispositions."New value: +"Policy id (UUID) from list_security_dispositions, or a repository_code disposition id from list_security_dispositions with scope repository_code."
    • addedInput schema / properties / scope
      Added value: +{
      +  "description": "repository_code when policy_id is a code finding disposition; optional, since the id is recognised either way.",
      +  "type": "string"
      +}
  2. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations already declare destructive=true, readOnly=false, and idempotent=false, but the description adds substantive behavior: findings return to open on the next read, the disposition remains on record as revoked with the reason, and the Ankra Pipelines image gate blocks again on its next run. It also names the required permission, security.manage, and is consistent with the annotations.

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?

The description is three tight sentences, front-loaded with the effect of revocation and followed by the downstream gate impact and usage guidance. Every sentence adds useful information without repetition.

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?

For a destructive mutation with no output schema, the description covers the immediate effect on findings, audit retention of the revoked disposition, required permission, and the repository_code/Pipelines consequence. An agent has enough context to decide whether to invoke it.

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 description coverage is 100%, so the schema already documents policy_id, reason, and scope. The description reinforces that repository_code dispositions affect the Pipelines image gate and that the reason is recorded, but adds little parameter-level syntax or format beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and resource: revoke a disposition, and explains what happens to covered findings and the disposition record. It does not explicitly name or contrast with a sibling such as update_security_disposition, so it falls short of full sibling differentiation.

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 gives clear when-to-use guidance: 'Use it when accepted risk is no longer acceptable or an acknowledgement or false-positive call was wrong.' It does not provide when-not-to-use guidance or name an alternative tool such as update_security_disposition.

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.