Skip to main content
Glama
CoveoSec
by CoveoSec

asm_management_remove_asm_data

Remove certificates, domains, and IP ranges from your inventory. Batch removal of up to 500 assets per request, including related subdomains and individual IPs.

Instructions

Remove Assets

Remove certificates, domains (paid-level domains and subdomains), and IPv4 address ranges from your inventory. Remove up to 500 certificates, domains, or IP ranges per request.

Removed assets appear the Asset Uploads/Removals table with the status Removed. Within 24 hours of submitting your request, assets are removed from the inventory. Within a few days, related incidents, alerts, and services are also removed. You cannot remove an asset that was uploaded in a previous upload request.

When you remove a paid-level domain, related subdomains are also removed. When you remove an IPv4 range, the individual IPv4 addresses in that range are also removed.

Required role: Instance Admin

Required license: Cortex XSIAM Premium or Cortex XSIAM with ASM add-on

[POST /public_api/v1/asm_management/remove_asm_data] · Asset Management

Example request body:

{
  "request_data": {
    "asset_type": "domain",
    "asset_identifiers": [
      "test1.com",
      "test2.com"
    ]
  }
}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
request_dataYesA dictionary containing the API request fields.
Behavior5/5

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

No annotations are provided, so the description carries the full burden. It discloses asynchronous removal (within 24 hours), cascading deletion of related items (incidents, alerts, services, subdomains, IPs), required role/license, and a specific limitation. This goes beyond typical descriptions.

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

Conciseness4/5

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

The description is well-structured and front-loaded, but longer than necessary due to multiple caveats. Every sentence provides useful context, so the length is justified. Could be slightly more compact without losing important details.

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 complex removal tool with no output schema, the description covers the full lifecycle: what gets removed, limits, timing, side effects, prerequisites, and an example. This is exceptionally complete and leaves little ambiguity.

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

Parameters3/5

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

The schema description coverage is 100%, so the description doesn't need to compensate. The example request body is helpful, but the tool description adds no new parameter semantics beyond what the schema already provides. The schema itself contains a minor error ('add' instead of 'remove') but that lies outside the tool description.

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 clearly states the tool's function: 'Remove certificates, domains ... and IPv4 address ranges from your inventory.' It uses a specific verb and resource, and distinguishes from the sibling 'asm_management_upload_asm_data' by focusing on removal.

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

Usage Guidelines4/5

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

Provides clear context on when to use: removal limits (up to 500), timing, cascading effects, and a constraint (cannot remove assets uploaded previously). Does not explicitly name an alternative tool, but the inverse relationship with the upload tool is implied.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/CoveoSec/xsiam-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server