secobserve-mcp

Delete SecObserve Record

secobserve_delete

DestructiveIdempotent

Permanently delete a SecObserve record with cascading removal of dependent data. Safeguards require exact name confirmation for products and product groups, ensuring deliberate deletion.

Instructions

Permanently delete a SecObserve record. Deletion cascades and cannot be undone.

Deleting a product removes its branches, observations, license components, metrics history and VEX documents; deleting a product group removes its child products too. Those two therefore require confirm_name to match the record's exact name, and the whole tool is disabled unless SECOBSERVE_ALLOW_DELETE is set on the server.

Args: resource (str): Resource name supporting delete. id (int): Primary key of the record. confirm_name (Optional[str]): Exact name; required for products and product_groups, case- and whitespace-sensitive.

Returns: str: A one-line confirmation naming what was deleted.

Examples: - Use when: "remove license policy item 88" -> resource="license_policy_items", id=88 - Use when: the user has explicitly confirmed deleting product 12 named "Example Product" -> resource="products", id=12, confirm_name="Example Product" - Don't use when: you want to stop tracking findings (assess them as "Not affected" or "Risk accepted" instead, which keeps the history).

Error Handling: Refused when SECOBSERVE_ALLOW_DELETE is unset, when the resource has no delete operation, or when confirm_name is missing for a product or product group. A 409 means something still references the record.

Input Schema

TableJSON Schema

Name	Required	Description
`id`	Yes	Numeric primary key of the record to delete.
`resource`	Yes	Resource name that supports delete.
`confirm_name`	No	Required for 'products' and 'product_groups': the record's exact name, case- and whitespace-sensitive. The API rejects a mismatch, which is what makes the delete deliberate.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed7 schema fields changedv0.3.0Sep 20, 2026

removedInput schema / $defs

Removed value: -{
-  "DeleteInput": {
-    "additionalProperties": false,
-    "description": "Input model for deleting a record.",
-    "properties": {
-      "confirm_name": {
-        "anyOf": [
-          {
-            "maxLength": 255,
-            "type": "string"
-          },
-          {
-            "type": "null"
-          }
-        ],
-        "default": null,
-        "description": "Required for 'products' and 'product_groups': the record's exact name, case- and whitespace-sensitive. The API rejects a mismatch, which is what makes the delete deliberate.",
-        "title": "Confirm Name"
-      },
-      "id": {
-        "description": "Numeric primary key of the record to delete.",
-        "minimum": 1,
-        "title": "Id",
-        "type": "integer"
-      },
-      "resource": {
-        "description": "Resource name that supports delete.",
-        "title": "Resource",
-        "type": "string"
-      }
-    },
-    "required": [
-      "resource",
-      "id"
-    ],
-    "title": "DeleteInput",
-    "type": "object"
-  }
-}

addedInput schema / additionalProperties
```
Added value: +false
```

addedInput schema / properties / confirm_name

Added value: +{
+  "anyOf": [
+    {
+      "maxLength": 255,
+      "type": "string"
+    },
+    {
+      "type": "null"
+    }
+  ],
+  "default": null,
+  "description": "Required for 'products' and 'product_groups': the record's exact name, case- and whitespace-sensitive. The API rejects a mismatch, which is what makes the delete deliberate.",
+  "title": "Confirm Name"
+}

addedInput schema / properties / id

Added value: +{
+  "description": "Numeric primary key of the record to delete.",
+  "minimum": 1,
+  "title": "Id",
+  "type": "integer"
+}

removedInput schema / properties / params

Removed value: -{
-  "$ref": "#/$defs/DeleteInput"
-}

addedInput schema / properties / resource

Added value: +{
+  "description": "Resource name that supports delete.",
+  "title": "Resource",
+  "type": "string"
+}

changedInput schema / required

Previous value: -[
-  "params"
-]New value: +[
+  "resource",
+  "id"
+]

First observedv0.1.2Sep 17, 2026

TDQS

A5/5.0

Behavior5/5

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

The description goes well beyond the destructiveHint annotation by detailing cascade behavior, irreversible consequences, product/product_group specifics, confirmation requirements, and error responses such as 409. This gives the agent a clear picture of what will happen and when the call is refused.

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 well-organized into paragraphs, Args, Returns, Examples, and Error Handling. Every section provides necessary operational context, and the most important warning about permanent cascading deletion is front-loaded.

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, cascading operation, the description covers prerequisites, behaviors, return values, error handling, and alternatives. The presence of an output schema reduces the need to describe return structure, and the provided one-line confirmation note is sufficient.

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

Parameters5/5

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

Though the schema already documents all three parameters, the description reinforces and enriches them with concrete examples, the case/whitespace sensitivity of confirm_name, and which resources require it. This adds practical semantics beyond the structured field definitions.

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

Purpose5/5

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

The description opens with 'Permanently delete a SecObserve record,' a specific verb and resource. It also differentiates itself from non-destructive alternatives by stating what not to use it for, such as stopping tracking findings.

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

Usage Guidelines5/5

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

Explicit 'Use when' and 'Don't use when' examples guide the agent to the correct invocation, including the alternative action of assessing findings instead of deleting. It also states prerequisites like confirm_name and the SECOBSERVE_ALLOW_DELETE server setting.

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

Deploy Server