Skip to main content
Glama
CISO Assistant MCP Server

CISO Assistant MCP Server

Api security exceptions destroy

ciso_assistant_api_security_exceptions_destroy
DestructiveIdempotent

Delete a security exception by ID in CISO Assistant, optionally confirming the destructive action when the client cannot prompt. Use it to remove obsolete or invalid exceptions.

Instructions

API endpoint that allows security exceptions to be viewed or edited.

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_security_exceptions_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.3/5.0
Behavior1/5

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

Annotations declare destructiveHint=true and readOnlyHint=false, but the description frames the tool as 'viewed or edited' and never mentions deletion, permanence, or irreversibility. This is a direct conflict with the supplied annotations; the confirm parameter's purpose and any permission or cascade consequences are also unaddressed.

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 a single short sentence, but brevity here comes from boilerplate rather than precision; the only sentence present mischaracterizes the operation, so nothing in it earns its place.

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, open-world, non-idempotent-flagged delete tool with no output schema, the description should at minimum state that it deletes a security exception and what happens on success. It provides none of that and instead implies a view/edit endpoint.

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 coverage is 50%: the 'confirm' parameter is documented in the schema, but 'id' is only typed as a string. The description supplies no meaning for either parameter, so it fails to compensate for the coverage gap on a destructive operation.

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

Purpose1/5

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

The description says the endpoint 'allows security exceptions to be viewed or edited,' which describes read/update behavior. The tool name and suffix indicate a destroy/delete operation, so the stated purpose is actively misleading rather than merely vague.

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 at all: no mention of when deletion is appropriate, no prerequisites, and no routing to alternatives such as security_exceptions_update, security_exceptions_partial_update, or security_exceptions_batch_action_create.

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