Skip to main content
Glama
CoveoSec
by CoveoSec

assets_get_assets_internet_exposure

Identify internet-exposed assets by filtering on business units, externally detected providers, inferred CVEs, MAC addresses, names, IPs, XDR agent presence, active external services, and type.

Instructions

Get all Internet Exposures

Get a list of all your Internet exposure filtered by business units, externally detected providers, externally inferred CVEs, mac addresses, names, IP addresses, whether it has an XDR agent, whether it has active external services, and type.

The maximum result limit is 500 assets.

Note: You can send a request to retrieve either all or filtered results.

Required license: Cortex XSIAM Premium or Cortex XSIAM Enterprise or Cortex XSIAM Enterprise Plus

[POST /public_api/v1/assets/get_assets_internet_exposure] · Asset management

Example request body:

{
  "request_data": {
    "filters": [
      {
        "field": "has_xdr_agent",
        "operator": "in",
        "value": [
          "n/a",
          false,
          true
        ]
      },
      {
        "field": "has_active_external_services",
        "operator": "in",
        "value": [
          false
        ]
      }
    ],
    "search_from": 0,
    "search_to": 500,
    "sort": {
      "field": "last_observed",
      "keyword": "desc"
    }
  }
}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
request_dataNoA dictionary containing the API request fields. An empty dictionary returns all results.
Behavior4/5

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

With no annotations, the description carries the full burden. It discloses the maximum result limit, required license tiers, the HTTP endpoint, and includes an example request. These add substantial behavioral context, though it stops short of detailing response structure or error conditions.

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 moderately long but every part serves a purpose: clear opening, explicit limit, license requirement, endpoint, and example. No filler. The example is necessary to illustrate the complex filter structure.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (nested filters, sort), the description covers the key operational aspects: the action, filters, limit, and license. Without an output schema, it doesn't detail the response fields, but for a 'get' operation this is a minor gap.

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

Parameters4/5

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

The input schema provides 100% coverage of parameter descriptions, but the description adds a concrete example body demonstrating how to structure filters, sort, and offsets. This goes beyond the schema and clarifies usage patterns for the nested objects.

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 'Get all Internet Exposures', a specific verb+resource that clearly distinguishes this from sibling asset tools (e.g., 'assets_get_external_service', 'assets_get_asset_internet_exposure'). It further lists the filterable fields, leaving no ambiguity about the tool's scope.

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?

The description states that you can retrieve 'all or filtered results' and notes the 500-asset maximum limit, providing clear context. However, it does not explicitly name when to use this tool over alternatives or state exclusions, so it stops short of full alternative guidance.

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