Skip to main content
Glama
CISO Assistant MCP Server

CISO Assistant MCP Server

Api iam auth tokens destroy

ciso_assistant_api_iam_auth_tokens_destroy
DestructiveIdempotent

Revoke an IAM authentication token by ID to invalidate access, with an optional confirmation flag for destructive operations.

Instructions

api_iam_auth_tokens_destroy

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": {
      "id": "<id>"
    },
    "name": "ciso_assistant_api_iam_auth_tokens_destroy"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
confirmNoExplicitly confirm this destructive operation. Needed only when the client cannot answer a confirmation prompt.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv2.3.12
    • addedInput schema / properties / confirm
      Added value: +{
      +  "default": false,
      +  "description": "Explicitly confirm this destructive operation. Needed only when the client cannot answer a confirmation prompt.",
      +  "type": "boolean"
      +}
  2. First observedv2.3.6

TDQS

D1.7/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, idempotentHint=true and openWorldHint=true, so the safety profile is covered structurally. The description adds nothing beyond that: it does not say what is lost when a token is destroyed (immediate session/API access revocation), whether the operation is recoverable, or what permissions are required. No contradiction with annotations, but zero added value.

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

Conciseness2/5

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

It is short, but brevity here is under-specification rather than conciseness: a single slug with no front-loaded statement of purpose, scope, or effect. There is no structure to speak of and nothing for the agent to act on.

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

Completeness1/5

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

For a destructive, security-sensitive IAM operation with no output schema and an undocumented required `id`, the description supplies none of the context an agent needs — no object identity, no effect, no prerequisites, no post-condition. It is completely inadequate relative to the tool's risk and complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 50%: the `confirm` parameter is documented in the schema but `id` is not, so the description is expected to compensate for that gap. It does not — there is no statement of what `id` identifies (token ID vs. user ID vs. token prefix) or how the client-side `confirm` flag interacts with the destructive flow.

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

Purpose2/5

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

The description is the literal tool slug repeated back ('api_iam_auth_tokens_destroy'), a tautology that restates the name and title without adding a verb-and-resource statement. An agent can infer from the name that an IAM auth token is being destroyed, but the description itself contributes nothing and gives no hint of which token, whose token, or what revocation means in this system.

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

Usage Guidelines1/5

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

There is no when-to-use guidance, no when-not-to-use guidance, and no mention of the very relevant siblings (ciso_assistant_api_iam_auth_tokens_create, _retrieve, ciso_assistant_api_iam_logout_create, ciso_assistant_api_iam_revoke_sessions_create) that an agent must choose between. The description does not even hint at the conditions under which deleting a token is the right action.

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

Deploy Server

Other Tools