Skip to main content
Glama
CISO Assistant MCP Server

CISO Assistant MCP Server

Api policies destroy

ciso_assistant_api_policies_destroy
DestructiveIdempotent

Delete a policy by ID from CISO Assistant, 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_policies_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.1/5.0
Behavior1/5

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

Annotations declare destructiveHint=true, readOnlyHint=false, and openWorldHint=true, but the description claims the endpoint is for viewing or editing. For a destructive tool this is the opposite of the disclosure an agent needs – no mention of irreversible data loss, cascading effects, or confirmation requirements.

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 is worthless here because the content is factually wrong. The one sentence it does contain is actively harmful rather than merely incomplete.

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 operation with a required identifier and a confirmation flag, an agent needs to know what is removed, whether it cascades, and when confirmation is mandatory. None of that is present, and the description's misleading framing leaves the agent less informed than the tool name alone.

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

Parameters1/5

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

Schema coverage is only 50%: the 'id' parameter has no description at all, and the 'confirm' parameter's schema description does the explanatory work. The description adds nothing about either parameter, so it fails to compensate for the coverage gap on the required argument.

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 tool is named policies_destroy, but the description never mentions deletion and instead says the endpoint 'allows applied controls to be viewed or edited' – the wrong resource and the wrong operation. An agent reading this cannot tell that this tool deletes a policy, nor distinguish it from the many *_retrieve and *_update siblings.

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 the confirm parameter's role in a destructive flow, and no pointer to alternatives. Worse, the description's 'viewed or edited' framing actively steers the agent toward calling it for read or update work.

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