Skip to main content
Glama
CISO Assistant MCP Server

CISO Assistant MCP Server

Api applied controls destroy

ciso_assistant_api_applied_controls_destroy
DestructiveIdempotent

Deletes an applied control by ID, with optional confirmation for destructive operations.

Instructions

API endpoint that allows applied controls 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_applied_controls_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.5/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 endpoint as one that allows records to be 'viewed or edited' and never mentions deletion, irreversibility, cascade effects, or the confirm flag. The description contradicts rather than supplements the annotation profile.

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 with no wasted clauses, but its brevity comes from under-specification rather than precision — it conveys no operationally useful information and is front-loaded with boilerplate ('API endpoint that allows...').

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 delete tool with no output schema and a partially undocumented schema, the description provides nothing an agent needs: not what is deleted, not the confirmation requirement, not consequences. It is wholly inadequate for the tool's risk profile.

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 carries its own description, but the required id parameter has none. The description adds no meaning about what id refers to (applied control identifier) or when confirm must be supplied, so it does not compensate for the coverage gap.

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 sentence names the resource (applied controls) but describes it generically as an endpoint that allows records to be 'viewed or edited', which does not identify the actual operation (destruction) signalled by the tool name. An agent cannot distinguish this from the many retrieve/update siblings from the description alone.

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 mention of prerequisites, and no reference to alternatives such as the update or retrieve siblings. Worse, the phrasing 'viewed or edited' actively points an agent toward read/edit usage for what is a delete operation.

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